Concurrent Testing
Run multiple tests at the same time.
Contrary to popular belief, performance tests do not have to be run one test at a time. In fact, it is more efficient to run multiple tests in parallel. This is because the combined runtime of the test takes only as long as the longest single test takes to run. Running tests concurrently can save hours, depending on the size of the tests and the number of tests previously fired sequentially. When code is checked in, or when a build is performed or a deployment is staged, the feedback needs to be as close to instant as possible. The idea of a four or five-hour test cycle every time a build is performed may have made sense in a nightly or weekly build world, but in the world of continuous delivery, "always have a working build" means proving the current build is working minutes or even seconds after it is run, not hours later.