Google's BAZEL stresses this: https://docs.bazel.build/versions/master/test-encyclopedia.html#role-of-the-test-runner https://docs.bazel.build/versions/master/t

Google's BAZEL stresses this: https://docs.bazel.build/versions/master/test-encyclopedia.html#role-of-the-test-runner https://docs.bazel.build/versions/master/test-encyclopedia.h... You can explain how much your test should take time, like: short(60secs), moderate(300sec), long(900sec), eternal(1hr, not really eternal hehehe). Then you can specify the special rules for testing, like: - exclusive - run no other test at the same time - external - test has an external dependency; disable test caching - large ... etc. etc. For example small, and fast unit test can be executed in parallel in machines (containers, whatever) with much smaller requirements, and compartmenalize better, to the point where it would be reasonable to set some strict rules - your "super-fast" unit test, should not eat that much memory, or you have to qualify it as such, and then it'll be treated differently. https://docs.bazel.build/versions/master/test-encyclopedia.html#role-of-the-test-runner https://docs.bazel.build/versions/master/test-encyclopedia.h...