Hi Team,
"gradle beast" takes -Ptests.iters=N and -Ptests.dups=M, to run many
iterations with and without new Random seed (I think), and you can pass it
a single test case e.g. "--tests TestRegexpRandom2".
But this seems to then run all test iterations on a single test JVM, even
if the gradle properties lists a high tests.jvms? At least, that's what
seems to be happening when I watch in "top".
Is there some simple way to beast a single test, many times, concurrently,
across many test JVMs?
Mike McCandless
http://blog.mikemccandless.com
"gradle beast" takes -Ptests.iters=N and -Ptests.dups=M, to run many
iterations with and without new Random seed (I think), and you can pass it
a single test case e.g. "--tests TestRegexpRandom2".
But this seems to then run all test iterations on a single test JVM, even
if the gradle properties lists a high tests.jvms? At least, that's what
seems to be happening when I watch in "top".
Is there some simple way to beast a single test, many times, concurrently,
across many test JVMs?
Mike McCandless
http://blog.mikemccandless.com