From the user guide:

> [...] The testNamePattern will be used to form an include pattern of "*/testNamePattern.class".

In other words, you can run individual test classes, but not individual test methods.

Thanks. That's what I feared

Hi!

I also had the need run single JUnit test methods from Gradle. I have created a [small project]([1]http://github.com/eric-thelin/junit-s...) on [GitHub]([2]http://github.com) that demonstrates how to implement a custom JUnit single test method runner and how to integrate it with Gradle. There are examples for both single and multi-project Gradle builds.

Check it out: [JUnit Single Method Runner]([3]http://github.com/eric-thelin/junit-s...)
----------------------------------------------------------------------------------------
[1] http://github.com/eric-thelin/junit-single-method-runner
[2] http://github.com
[3] http://github.com/eric-thelin/junit-single-method-runner

Nice, Eric. Thanks for sharing.

Curious, is there a feature request filed for this anywhere?

Thanks for filing this. I would really like to see this added if possible. When running tests as I develop, it is nice to be able to run just one single test method at a time so as to not be distracted by the other tests and focus on the one I'm working on at the moment. (I currently do this with maven and it is working out quite well. It is not a dealbreaker for transitioning to gradle or not, but I think it will reduce productivity.)

I downloaded the source for gradle from github and did a grep for `test.single` and didn't see any references to it anywhere that looked significant. Where should I poke around in the code to look at supporting this?

The testTask.single handling is done in org.gradle.api.plugins.JavaBasePlugin. Supporting execution of single test methods will require a somewhat bigger change though.

Took a look at this briefly last night. Looks like it would involve a change of `JUnitTestClassExecuter` to use `Request.method`, a change of `TestNGTestClassProcessor` to use `testNg.setTestNames()`, as well as some logic further up the stack that parses out the 'single' property for test names (after the "#" sign, separated by "+" signs like surefire?) – and passes those down the stack to the test class processor to handle them if present.

Supporting test name wildcards would be tricky since the test frameworks themselves don't appear to support that – as it would require doing some reflection to find matching test methods to the patterns – but that doesn't seem necessary for a first version of supporting single test methods.

FYI. I have something working right now with testng and junit. It's pretty sweet. The format goes like this:

`gradle test -Dtest.single=TestClass#method1,method2`

TestNG needed a bit more extensive a change than I had thought, and it has broken most of the testng test processor test cases. After I get those fixed I will submit a pull request.

Submitted. https://github.com/gradle/gradle/pull/193

I suggest this ticket should be re-opened as the implemented feature does not work.

I just downloaded gradle 1.11 and it still does not work. It is mentioned in the above linked pull request (#193) that others have reported similar issues, however, I don't see anything in the "known issues" for 1.10 or 1.11 about this. I'm a bit disappointed that another release has gone by without fixing this released feature...

I'm assuming there has been no progress on this?

update: found the comments here
https://github.com/gradle/gradle/pull/193

So far, we haven't been able to reproduce the misbehavior reported late in this thread. If you can provide a reproducible sample we will surely fix any problem. I use --tests flag very often in many projects and it works for me

Sorry, I did finally sort it out and get it working.

we have our on Runner implementation, and it took us to push the filter method down to the children.