I would look into partitioning the tests into batches, so that keystone
tests are in earlier batches and fine grained tests are in later batches.
I would also pull all the fast tests into earlier batches.
If you collect the average test execution time for each test case, you can
sort tests based
Thanks Mark. This is the parallelization path. Besides, are there any other
advices/best practice tips on how to "manage" such a fast-growing
regression suite?
Yana
On Fri, Aug 9, 2013 at 6:34 PM, Mark Waite wrote:
> There are several levels at which you could run your JUnit tests in
> parall
There are several levels at which you could run your JUnit tests in
parallel. Most of them don't involve anything with Jenkins, other than
using Jenkins to start them executing.
For example
- Use JUnit 4.7 to run the tests in parallel, see [1] and [2]
- Use gradle to run your tests, see
