Open divanov-ki opened 11 hours ago
Worth noting that more conservative runs with less scenarios executed generate the report just fine
I realise this issue is actually a duplicate of https://github.com/prashant-ramcharan/courgette-jvm/issues/410. You can treat it as a confirmation that it's still an issue for extended test runs
Hi, I'm not sure if it's related to https://github.com/prashant-ramcharan/courgette-jvm/issues/410 as in this case the report generation was attempted whereas in issue 410 the report generation failed completely, likely related to JVM out of memory.
The issue here seems to be the parsing of the json file.
You should see a courgette-report-processing-errors.txt
if the are any processing errors.
com.google.gson
dependency defined in your build.gradle or pom file? If so, what version are you using?reportTargetDir
)json
plugin in your runner (i.e. Courgette runner -> cucumberOptions -> plugin -> json:some-path
) enabled? Have you tried disabling to test?
@prashant-ramcharan I bumped courgette-jvm from
6.13.0
to6.17.0
(and subsequently to6.18.0
to see if behaviour is different) and the reporting broke with the following exception thrown:For context our test run includes 300+ scenarios executed, so quite a bit of test related metadata generated to support the report generation at the end of execution. Could this be related to the bugfix you added in
6.17.0
to resolve the creation of parent directories for reporting issue?