customization of Allure Report before rendering (expand failed step or sub-step by default)

[wvdb]

When we render an allure report with the allure generate command we would like to fine-tune the allure-report from a UI perspective.

By example: we have a step with multiple levels and we would like to see the final (failing) sub-step at a glance without having to click on every single hyperlink. Or in a nutshell: to expand the failed step or sub-step by default.

allure-report AS IS:

allure-report TO BE:

Is it possible to list down a few bullet points with the modifications to be done (assuming this is feasible)?

Thanks in advance!

[baev]

The request is already implemented in Allure 3

[wvdb]

Ok, thanks for fast reply. Appreciated.

But it seems Allure 3 is still in development mode. Are we able to install Allure 3 already (currently all installation procedures mention Allure 2.32.2)? I verified https://github.com/allure-framework/allure3 but the installation procedure is rather short (and we are stuck currently).

[baev]

Yes, it's still in early beta. You can take a look at it here https://allure-framework.github.io/allure3/

It's already usable, so you can subscribe for the updates and give it a try. All the feedback is appreciated. The documentation will be added later.

Allure 3 is fully reworked using Node (requires Node 18 or above to run). It can be installed via NPM (https://www.npmjs.com/package/allure).

Execute npx allure --help to see all the available commands. The main use cases:

1. Generate the report based on existing allure-results:

   $ npx allure generate path/to/allure-results # to generate the report with default config
   $ npx allure open # open the report

2. Run the tests and generate the report. Let's say you use ./gradlew test command to run the tests. Then, to execute such command and generate the report, you may use

   $ npx allure run -- ./gradlew test # to run command and generate the report afterwards. It will detect location of allure-results automatically
   $ npx allure open # open the report

[wvdb]

Thanks again for valuable input. We discussed internally. Since our use-case only requires a rather basic evidence-report, we decided to use a Java based template engine to support our MVP. We'll reconsider Allure 3 in the long run.