I'm submitting a ...
What is the current behavior?
test, running from dataprovider, where data could have arrays - fails with ClassCastException
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior?
Having arrays as parameter not hurting for test
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
| Allure version |
2.3.1 |
| Test framework |
testng@6.8 |
| Allure adaptor |
allure-testng@2.0-BETA16 |
| Generate report using |
allure-maven@2.18 |
Other information
testSomeTest(String param1, boolean param2, int[] param3, int[] param4, boolean param5)
Parameters: [priority, false, [0, 4, 1, 2, 3, 5], [1, 3, 5], false]
java.lang.ClassCastException: [I cannot be cast to [Ljava.lang.Object;
at io.qameta.allure.testng.AllureTestNg.convertParameterValueToString(AllureTestNg.java:589)
at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:545)
at java.util.stream.AbstractPipeline.evaluateToArrayNode(AbstractPipeline.java:260)
at java.util.stream.ReferencePipeline.toArray(ReferencePipeline.java:438)
at io.qameta.allure.testng.AllureTestNg.getParameters(AllureTestNg.java:580)
at io.qameta.allure.testng.AllureTestNg.onTestStart(AllureTestNg.java:205)
at org.testng.internal.Invoker.runTestListeners(Invoker.java:1904)
at org.testng.internal.Invoker.runTestListeners(Invoker.java:1879)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:685)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
at org.testng.TestRunner.privateRun(TestRunner.java:767)
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.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:72)
at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:123)
I'm submitting a ...
What is the current behavior?
test, running from dataprovider, where data could have arrays - fails with ClassCastException
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior?
Having arrays as parameter not hurting for test
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Other information