Repository navigation
Tests are not starting with Allure-testng 2.9.0 and TestNG 6.11 #314
Description
I'm submitting a ...
- bug report
- feature request
- support request => Please do not submit support request here, see note at the top of this template.
What is the current behavior?
I'm using TestNG 6.11. If I'm changing Allure-testng version from 2.8.1 to 2.9.0 I'm getting an error on tests execution start. StackTrace is attached.
TestNG version 6.14.3 works with Allure 2.9.0 as expected. But TestNG version 6.14.3 doesn't suite us because of multiple bugs.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
- Use Allure-testng 2.9.0 and Testng 6.11
- Use any test and run as xml suite
Error appears:
java.lang.NoSuchMethodError: org.testng.internal.TestResult.<init>(Ljava/lang/Object;Lorg/testng/ITestNGMethod;Ljava/lang/Throwable;Lorg/testng/ITestContext;)V at io.qameta.allure.testng.AllureTestNg.createFakeResult(AllureTestNg.java:171) at io.qameta.allure.testng.AllureTestNg.lambda$onStart$1(AllureTestNg.java:167) at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184) at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1548) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151) at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418) at io.qameta.allure.testng.AllureTestNg.onStart(AllureTestNg.java:167) at org.testng.TestRunner.fireEvent(TestRunner.java:1184) at org.testng.TestRunner.beforeRun(TestRunner.java:621) at org.testng.TestRunner.run(TestRunner.java:594) at org.testng.SuiteRunner.runTest(SuiteRunner.java:380) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:375) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:340) at org.testng.SuiteRunner.run(SuiteRunner.java:289) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1301) at org.testng.TestNG.runSuitesLocally(TestNG.java:1226) at org.testng.TestNG.runSuites(TestNG.java:1144) at org.testng.TestNG.run(TestNG.java:1115) at org.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:72) at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:123)
What is the expected behavior?
Tests are starting and passing. I expect to have the same behavior in 2.8.1 version and 2.9.0
What is the motivation / use case for changing the behavior?
Fixing the crash
Please tell us about your environment:
| Allure version | 2.9.0 |
|---|---|
| Test framework | testng@6.11 |
Activity
remove testng internal api usage (fixes #314, fixes #308, via #321)
cristianvasiliu commentedon Apr 6, 2020
When trying to run Maven specific lifecycle project commands, like Test and Plugins-Surefire-Test:
If I'm using following dependencies:
allure-testng v2.9.0andtestng v7.0.0then I'm getting same error.When I use
testng v.7.1.0then I'm gettingfollowing error:org/testng/IInvokedMethodListener2When I use below configuration, then tests are loaded successfully, but I can see only passed ones and with this mention:
[AppClassLoader@18b4aac2] warning javax.* types are not being woven because the weaver option '-Xset:weaveJavaxPackages=true' has not been specifiedIf I'm using below config then tests can run successfully
baev commentedon Apr 6, 2020
@cristianvasiliu FYI please do not comment on closed issues
The support of testng 7+ was introduced in 2.13.2
this is aspecj warning, you can configure aspectj weaver to disable processing of javax.* types in order to get rid of it. BTW this warning should not affect your tests run and allure
cristianvasiliu commentedon Apr 6, 2020
@baev ok, thanks for the FYI and for the hint
cristianvasiliu commentedon Apr 7, 2020
Do you know @baev how to configure aspectj weaver to disable processing of javax.* type ? :) I couldn't find anywhere else to ask you this :D