Changes in Version 3.6.2 (2021-01-22)
Changes in Version 3.5.0 (2020-06-04)
Changes in Version 3.4.2 (2020-03-26)
Changes in Version 3.3.1 (2019-08-22)
Changes in Version 3.3.0 (2019-01-09)
Changes in Version 3.2.1 (2018-12-21)
Changes in Version 3.2.0 (2018-08-27)
Changes in Version 3.1.1 (2018-06-29)
Changes in Version 3.1.0 (2018-03-27)
Changes in Version 3.0.0 (2018-02-20)
Allure is a framework/tool which generates comprehensive reports for your test executions. This happens in two steps:
- The test results are captured and written to json files
- The json files are transformed into beautiful reports
Please consult the Allure website to obtain further information about Allure.
The Allure module acts as an adapter between tapir’s Notification API and Allure’s Reporting API. If the optional module is in the classpath at test runtime, the corresponding xml files are generated. These xml files are picked up by Allure and transformed into a good-looking report.
<dependency> <groupId>io.tapir-test</groupId> <artifactId>tapir-extensions-allure2</artifactId> <version>1.3.0</version> </dependency>
The screenshot below displays a sample test execution report.
In general you can just use this command:
> mvn clean test allure:serve
Maven fires up a web server and starts the browser which renders the Allure report.
Allure provides a plugin for Jenkins. Please consult the documentation on their website, but in general the defaults are fine to work with tapir.
The Allure Report is stored for every build and you can switch from the Jenkins UI to the Allure report and vice versa.