Any test that doesn't really do anything in setup/teardown seems like a
good candidate for using tests.iters, which will be much faster.
For SolrCloud level tests beasting is becoming my first choice.
For a lot of the Lucene level code tests.iters makes a lot of sense so
it's too useful to remove.
On Mon, Jan 15, 2018 at 7:56 AM, Jason Gerlowski <[EMAIL PROTECTED]> wrote: