Reorder tests based on execution time

[sebastianbergmann]

Thanks to the caching of test results, we know how long it took to execute each test the last time.

It could make sense to reorder tests based on execution time: fast tests first, slow tests last.

@epdenouden What do you think?

[epdenouden]

Technically that is super easy, the current sorter will already use the time when it the 'defect severity' is the same.

Personally I have never found a use case for just sorting by time. The quickest tests are always these loooong lists of @dataprovider tests for input validation, parsers and minor logic building blocks. These tests all count as one per data row which makes them super fast and you're still stuck with this huge testMyInputAgainstAllUTFWeirdness as @dataprovider-driven tests become a DataproviderTestSuite when running.

But hey, it's a simple thing that might help somebody out IRL. :)