Home/ Questions/Q 8175829
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-06T22:55:02+00:00

From time to time I run into the issue that Grails integration tests the

  • 0

From time to time I run into the issue that Grails integration tests the name of which ends in “IntegrationTests” don’t work coming up with exceptions that show that GORM methods have not been added to domain classes. After renaming those tests to “*IntegrationTest” (no s at the end) they work fine.

A short example:

class MyIntegrationTests {
    @Test
    void myTest() {
        assert MyDomainClass.count() == 0
    }
}

Will fail with the following exception:

Failure:  myTest(de.myproject.MyIntegrationTests)
  groovy.lang.MissingMethodException: No signature of method: de.myproject.MyDomainClass.count() is applicable for argument types: () values: []
Possible solutions: count(), ident(), print(java.io.PrintWriter), print(java.lang.Object), getCount(), wait()
at de.myproject.MyIntegrationTests.myTest(MyIntegrationTests.groovy:9)

After renaming MyIntegrationTests to MyIntegrationTest the test passes.

Is there some kind of magic happening according to the test’s name? All I found in Grails documentation is: “Tests can also use the suffix of Test instead of Tests. ” Any ideas?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I eventually found the cause for the different behaviour of “*Test” and “*Tests” myself: Different postfixes change the order in which the tests are being run. To make things worse, the exact order is platform-dependent. Thus, my tests ran locally (OSX) in a different order than on my CI machine (Linux), and thereby produced different results.

    Why the exception occurrs in some order is a totally different problem, though, which I haven’t figured out (yet).

    • 0