You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Trying to Run a Citrus Test with a TestNG dataProvider, although it is possible to use a dataProvider Name that does not correspond to the method Name and also to set a dataProviderClass, the Citrus Framework tries to find a method in the same class with the name of the dataProvider. This limitation does not exist in the TestNG framework, is not documented and results in the test run to be terminated without any useful message. Only in the TestNG Report I was able to find following stack trace:
java.lang.NullPointerException
at com.consol.citrus.testng.AbstractTestNGCitrusTest.resolveParameter(AbstractTestNGCitrusTest.java:120)
at com.consol.citrus.testng.AbstractTestNGCitrusTest.resolveParameter(AbstractTestNGCitrusTest.java:124)
at com.consol.citrus.dsl.testng.TestNGCitrusTest.invokeTestMethod(TestNGCitrusTest.java:128)
at com.consol.citrus.dsl.testng.TestNGCitrusTest.run(TestNGCitrusTest.java:100)
at com.consol.citrus.dsl.testng.TestNGCitrusTest.run(TestNGCitrusTest.java:58)
at org.testng.internal.MethodInvocationHelper.invokeHookable(MethodInvocationHelper.java:201)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:642)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:811)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1137)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
at org.testng.TestRunner.privateRun(TestRunner.java:753)
at org.testng.TestRunner.run(TestRunner.java:607)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:368)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:363) [..]
Through debugging it was clear that org.springframework.util.findMethod was called with the providerName as method name, which is not correct in that case
The text was updated successfully, but these errors were encountered:
When Trying to Run a Citrus Test with a TestNG dataProvider, although it is possible to use a dataProvider Name that does not correspond to the method Name and also to set a dataProviderClass, the Citrus Framework tries to find a method in the same class with the name of the dataProvider. This limitation does not exist in the TestNG framework, is not documented and results in the test run to be terminated without any useful message. Only in the TestNG Report I was able to find following stack trace:
java.lang.NullPointerException
at com.consol.citrus.testng.AbstractTestNGCitrusTest.resolveParameter(AbstractTestNGCitrusTest.java:120)
at com.consol.citrus.testng.AbstractTestNGCitrusTest.resolveParameter(AbstractTestNGCitrusTest.java:124)
at com.consol.citrus.dsl.testng.TestNGCitrusTest.invokeTestMethod(TestNGCitrusTest.java:128)
at com.consol.citrus.dsl.testng.TestNGCitrusTest.run(TestNGCitrusTest.java:100)
at com.consol.citrus.dsl.testng.TestNGCitrusTest.run(TestNGCitrusTest.java:58)
at org.testng.internal.MethodInvocationHelper.invokeHookable(MethodInvocationHelper.java:201)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:642)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:811)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1137)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
at org.testng.TestRunner.privateRun(TestRunner.java:753)
at org.testng.TestRunner.run(TestRunner.java:607)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:368)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:363) [..]
Through debugging it was clear that org.springframework.util.findMethod was called with the providerName as method name, which is not correct in that case
The text was updated successfully, but these errors were encountered: