-
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)
Running your tapir Tests
JUnit
tapir tests can be executed as JUnit tests. Therefore it’s possible just to perform Run As -> JUnit Test in Eclipse to start the test. For this to work you need to include the JUnit modules for tapir.
<dependency>
<groupId>de.bmiag.tapir</groupId>
<artifactId>tapir-junit</artifactId>
</dependency>
<dependency>
<groupId>de.bmiag.tapir</groupId>
<artifactId>tapir-junit-execution</artifactId>
</dependency>
Standalone
tapir test suites can be started standalone. For every class annotated with @TestSuite or @TestClass a main method is generated, which means that it can be started as a Java application.
You can also run the test suite or class from the commandline:
> java de.bmiag.example.MyTestClass
CLI
tapir provides a dedicated cli module which can be used to run test suites or classes. Currently this module does not provide any advantages compared to the way introduced in the last chapter, but later on you might be able to provide some custom properties which influence the execution.
Dependency
<dependency>
<groupId>de.bmiag.tapir</groupId>
<artifactId>tapir-cli</artifactId>
</dependency>
Example
The TapirLauncher contains a main method, which means you can start it via the command line. The class to be executed is given as parameter.
> java de.bmiag.tapir.cli.TapirLauncher de.bmiag.example.MyTestClass
- Previous
- Next