Short answer: don't use tests.iters. Use ant beast.

Long answer: It has been discussed on the list several times.
tests.iters does not do what a lot of people seem to think.
From what i remember: it creates your test *class* a single time and
runs stuff repeatedly... I think only (new *instance*, setup,
teardown, etc). I don't even think it runs e.g. beforeclass/afterclass
stuff between iterations either, but that still wouldnt make it
completely safe anyway unless the whole class was recreated (a test
could leave a static variable in a different state or something).

So if your test isn't a pure unit test, its probably not ready for
tests.iters. Just use ant beast, it works :)

On Thu, Jan 11, 2018 at 12:48 PM, Erick Erickson

NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB