Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reports not generated #404

Closed
MadhuQAAutomation opened this issue Apr 11, 2024 · 9 comments
Closed

Reports not generated #404

MadhuQAAutomation opened this issue Apr 11, 2024 · 9 comments

Comments

@MadhuQAAutomation
Copy link

MadhuQAAutomation commented Apr 11, 2024

Hi @prashant-ramcharan - Using the courgette test runner, I ran my test suite from the command line using 'mvn verify'. After completion of the test, I got the below error and no reports were generated.

Courgette Version : 6.13.0

What could be the issue?

`───────────────────────────────────────────────────
Courgette Test Statistics
───────────────────────────────────────────────────
Summary: 97% passed, 3% failed
Duration: 408 min, 3 sec
Run Level: Feature
Total: 302
Passed: 294
Failed: 8
───────────────────────────────────────────────────

[Courgette Runner] There was an unexpected error processing the individual Cucumber report files and Courgette was unable to create any reports for this test run.`

I am running the test through junit and below is my test runner configuration.

Test Runner:

@RunWith(Courgette.class)
@CourgetteOptions(
threads = 1,
disableHtmlReport = HtmlReport.COURGETTE_HTML,
reportTargetDir = "target",
runLevel = CourgetteRunLevel.FEATURE,
testOutput = CourgetteTestOutput.CONSOLE,
classPath = {"target/libs/*", "target/classes/"},
persistParallelCucumberJsonReports = true,
cucumberOptions = @CucumberOptions(
snippets = SnippetType.CAMELCASE,
features = "src/test/resources/features/policies",
glue = {"com.automation.steps"},
plugin = {
"pretty",
"json:src/test/json/cucumber.json",
"html:reports/html-report/automation-report.html",
"junit:reports/xml/cucumber.xml"
}
))
public class TestRunner {
}

@prashant-ramcharan
Copy link
Owner

Hi @MadhuQAAutomation

Courgette combines the reports at the end of the test run and if one of the reports are corrupt / missing the library would be unable to merge all reports into a single report at the end of the run.

As you ran 302 tests this means there were 302 reports stored in memory waiting to be merged into 1 report at the end of the test run and it's likely that one or more reports were not processable.

Have you seen this happen again on a recent run?

@MadhuQAAutomation
Copy link
Author

MadhuQAAutomation commented May 14, 2024 via email

@MadhuQAAutomation
Copy link
Author

MadhuQAAutomation commented Jun 7, 2024

@prashant-ramcharan - I reran the test suite and got the same error again and the HTML Report is not generated.

image

@prashant-ramcharan
Copy link
Owner

How many tests did you run by the way?

@MadhuQAAutomation
Copy link
Author

MadhuQAAutomation commented Jun 7, 2024 via email

@MadhuQAAutomation MadhuQAAutomation changed the title Reports not genenated Reports not generated Jun 11, 2024
@prashant-ramcharan
Copy link
Owner

prashant-ramcharan commented Jun 12, 2024

That doesn't seem a lot to be fair.

I plan on optimising the report processing in a future Courgette release.

@MadhuQAAutomation
Copy link
Author

MadhuQAAutomation commented Jun 13, 2024

@prashant-ramcharan - Thanks for the update. Also wanted to check if there is any plan to support the generation of courgette reports with multiple JSON files as part of the report optimization.

@prashant-ramcharan
Copy link
Owner

@MadhuQAAutomation could you elaborate please?

Do you mean generating a Courgette report using multiple Cucumber JSON files outside of a test run?

@MadhuQAAutomation
Copy link
Author

@prashant-ramcharan - That's right. If I have 4 different stages in my pipeline and the 4th step is the generation of reports, I want the reports to be generated by reading the JSON files of stage1-3 which are located in the same folder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants