On 8/06/10 8:38 AM, Peter Niederwieser wrote:
Adam Murdoch-3 wrote:
One possible hook we could provide is to allow you to provide a custom
TestClassProcessor implementation, which decorates the built-in one.
Would this allow me to freely reorder test classes without losing any
Gradle-provided testing features like running tests in parallel?
Yes.
Adam Murdoch-3 wrote:
An option would be to introduce a public API which looks
something like TestClassProcessor, but which we can keep a bit more
stable.
How about just letting me provide an ordered list of classes to the test
task? Or a comparator?
This is a possibility. How would the list of classes work? Would you
take over the test detection?
I wanted something general purpose, which could do whatever filtering
and reordering (or duplication or failure thresholds or whatever) it
wants. And then, later, we would add convenience methods which take,
say, a comparator.
I'm curious how you plan to decide which tests are more likely to fail,
and what information you will need Gradle to provide?
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
CTO, Gradle Inc. - Gradle Training, Support, Consulting
http://www.gradle.biz
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
