[SUREFIRE-1038] Regression: Method depends on nonexistent group

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.16
• Fix Version/s: 2.17
• Component/s: TestNG support
• Assignee: Andreas Gudian
• Reporter: Gili
• Created: 09/Oct/13 13:51
• Updated: 27/Oct/14 13:58
• Resolved: 03/Jan/14 14:27

Description

Version 2.16 contains a regression that prevents the use of TestNG groups. Version 2.15 works fine.

When I run my unit tests I get the following error:

Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on project web.backend: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.16:test failed: There was an error in the forked process
org.testng.TestNGException:
DependencyMap::Method "CallTest.createCall()[pri:0, instance:com.vtlr.web.backend.resource.CallTest@53635ac1]" depends on nonexistent group "department"
at org.testng.DependencyMap.getMethodsThatBelongTo(DependencyMap.java:46)
at org.testng.TestRunner.createDynamicGraph(TestRunner.java:1074)
at org.testng.TestRunner.privateRun(TestRunner.java:734)
at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1149)
at org.testng.TestNG.run(TestNG.java:1057)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:91)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)

I checked and group "department" exists. Furthermore, downgrading back to 2.15 makes the problem go away.

Issue Links

• is related to: SUREFIRE-1044 Changed behaviour of TestNG test execution after implementing runOrder support