As I've learned today, the correct way to run a single test class is "-D<testTaskName>.single=FooTest". (Before I had thought that it's always "-Dtest.single=FooTest".) How about using a fixed system property instead? This would make the feature easier to use.
One potential downside of using a fixed system property is that it would make it more difficult to fail the build if the naming pattern doesn't match anything (we would have to consider all test tasks to make this decision). But since this feature is mostly used interactively, I don't even consider it essential (though probably desirable) to fail the build. Since -Dtest.single is really about running a subset of tests, I also wonder if we could come up with a better name (e.g. -Dtest.include). But this is a minor complaint. Thoughts? -- Peter Niederwieser Developer, Gradle http://www.gradle.org Trainer & Consultant, Gradle Inc. http://www.gradle.biz Creator, Spock Framework http://spockframework.org -- View this message in context: http://gradle.1045684.n5.nabble.com/Simplifying-the-execution-of-single-test-classes-tp3394412p3394412.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
