automated-testsgherkinalluretest-reportingreqnroll

Reqnroll Allure report generation problems


I have a test solution, built on:

My solution builds, discovers and executes the tests as expected.

However, I have run into some issues when trying to generate the Allure report (i.e. when attempting to generate HTML output report from JSON format test results and container files).

For regular scenarios, and those with in-step parameter tables, the AllureReport.Generator outputs the report as expected.

But, for test scenario outlines using examples tables (parameterized tests pattern), although the tests execute and output a JSON result and container file for each interative execution, the ReportGenerator fails to create any corresponding content in the report.

According to Allure documentation, each row in the examples table should execute as a separate scenario. The documentation also states

"Allure Reqnroll automatically recognizes this pattern. No additional configuration is required."

https://allurereport.org/docs/reqnroll-reference/#scenario-outlines

I'm under some pressure to resolve this issue and provide human-readable reports for my test outputs. I'd appreciate any insights or guidance that might help.

Thanks for looking.

*** UPDATE ***

I'm still struggling with this issue: i.e. Allure report for Reqnroll test run fails to pick up test result output from parameterized pattern tests with Examples tables.

I did stumble on this stackoverflow post from 2019, indicating a problem with test scenarios with the same name but in different features failing to report to Allure: Why is only a few results are shown in allure report

This may be related to the issue I'm experiencing: I note that when I look into the results.json files for the parameterized test executions, scenario name for each iteration is indeed the same.

Could this be the problem (contrary to the Allure documentation's assurances that the parameterized tests pattern from Reqnroll was automatically recognised by Allure)??

If this is indeed the problem, is there any way to workaround it?

*** UPDATE *** My stack has now been updated like so:

Problems persist i.e. Allure fails to report on execution of any parameterized Reqnroll test (non-parameterized tests report as expected).

Question: in spite of the claims in Allure documentation (above), has Allure ever actually worked to produce reports for tests of this type?

Has anyone ever successfully implemented Allure reporting for Reqnroll tests?

Is it possible? Or should I abandon it and search for a more reliable and useful test reporting framework?

Urgent insights and advice needed here. Thanks.


Solution

  • AllureReport.Generator 0.1.0 isn't an official integration. It's not been maintained since 2018, so please don't use it. According to the package explorer, it has bundled Allure Commandline version 2.7.0 (released in 2018).

    Please try to use one of the official Allure distributions: https://allurereport.org/docs/install/