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)
This module contains an implementation of tapir’s execution listener, which can be used as a base for concrete reporting classes. To use it, you simply need to add it as Maven dependency.
<dependency> <groupId>io.tapir-test</groupId> <artifactId>tapir-extensions-reporting-base</artifactId> <version>1.3.0</version> </dependency>
tapir’s default implementations use either frameworks which have to be notified about each event (JUnit) or have an internal model, which stores the events (Allure). However, some people might want to develop reporting listeners which simply convert the resulting execution at the end into a report instead of listening to each single execution event. The tapir extensions reporting base provides the AbstractBaseReportingListener class which collects all the events during the execution. The concrete implementation of this class is informed after the execution and is provided with tapir’s execution plan and a mapping to retrieve information about the execution.