We definitely plan to do some kind of test optimization in the next release or two. In fact the Bamboo (Atlassian’s CI offering) guys are pretty keen on making test optimization an out of the box option if you also have Clover installed which could be really nice.

Good to meet you back at CITCON Sydney. Clover 2 will include similar functionality - the ability to determine a subset of tests to run based on what source files have changed.

JTestMe certainly was an elegant use of Aspects - one that could potentially replace the obligatory “logging” example that Aspectinado’s like to proffer We don’t use Aspects simply because we don’t need to - our instrumentation already collects the necessary data to determine which tests hit which statements.

Of course, as we discussed at the time, the assumption being made here - tests that execute over changed code are the only ones that will test that code - doesn’t always hold. Obviously running all the tests regularly is still prudent

Clover 2 will also provide something similar to ProTest - allowing prioritising based on changed code, coverage and speed, so that tests that provide the most coverage the quickest are run first, the idea here being that your test suite should fail fast.

Cheers,
-Brendan