Running a single test method from test suite

To accomplish this I have modified the TestApp script from Grails distribution. It is attached as TestApp2.groovy. The approach taken by me is sort of hacky and not that clean. To execute the individual testMethods I added

class GrailsMethodTestSuite extends GrailsTestSuite {
private def methodNames
private def clazz
public GrailsMethodTestSuite(applicationContext,clazz,methods)

public void addTest(Test test)

def addTestMethods(){
TestSuite ts = new TestSuite(clazz) //create a testsuite so as to get testnames
for (Enumeration e= ts.tests(); e.hasMoreElements(); ) {
def test= e.nextElement();
if(this.methodNames.contains(test.name))

}
}
}

In the script only and modified few parts so as to use GrailsMethodTestSuite if any test method is specified . By default the script uses GrailsTestSuite if no method is specified. The above suite would eat up any test methods added during testsuite initialization and later adds the one we are interested in.

Modified TestApp script to execute individual test methods

First, thanks for the patch!

Second, the following code in TestApp:

            // If the test name includes a package, replace it with the
            // corresponding file path.
            if (it.indexOf('.') != -1) {
                 if(containsMethodName(it)){//filter out te method name
                     it = it.substring(0,it.lastIndexOf('.'))
                 }
                 it = it.replace('.' as char, '/' as char)
            }
            else {
                // Allow the test class to be in any package.
                it = "**/$it"
            }

            return "${it}Tests"

should probably be:

            if (containsMethodName(it)) {//filter out te method name
                it = it.substring(0,it.lastIndexOf('.'))
            }

            // If the test name includes a package, replace it with the
            // corresponding file path.
            if (it.indexOf('.') != -1) {
                 it = it.replace('.' as char, '/' as char)
            }
            else {
                // Allow the test class to be in any package.
                it = "**/$it"
            }

            return "${it}Tests"

In other words, you should filter out the method name before checking for a package.

Finally, it would probably be best to modify GrailsTestSuite to use the default TestSuite constructor when method names are supplied, and then manually add the tests using 'addTest(TestSuite.createTest(clazz, methodName)'.

In fact, it might be a good idea to have GrailsTestSuite handle the <class>.<method> form directly.

Hi Peter

Filtering out method name is more cleaner. I gone this way as it did not required creating any java class so sort of quick and dirty way. Ideally GrailsTestSuite should handle the test methods directly.

Implemented in such a way that you can run:

grails test-app MyService.testSomeMethod

This doesn't seem to work in 1.3.1, but does in 1.2.2.

Create simple grails app, add a domain class nz.Foo, edit FooTests, add two methods testA, testB.

Then running grails test-app nz.testA runs both testA and TestB.

Doing the same steps under 1.2.2, only runs testA.

Is this a known issue?

In grails 1.3 we are also facing the issue where a single integration test could not be run. It runs the entire test file.

@boojapathy & @Mark Berger: Yes, this has been fixed for 1.3.2