1
0
mirror of https://github.com/jetty/jetty.project.git synced 2025-02-16 19:45:05 +00:00
jetty.project/jetty-maven-plugin/README_INTEGRATION_TEST.md
Miron Balcerzak 4c11f245c9 Fixes jetty-maven-plugin - transitive deps in single war project ()
* Issue  jetty-maven-plugin - transitive deps in single war project

Signed-off-by: Miron Balcerzak <mironbalcerzak@gmail.com>

* Issue  jetty-maven-plugin - code review fixes

Signed-off-by: Miron Balcerzak <mironbalcerzak@gmail.com>

* Issue  jetty-maven-plugin - code review fixes

Signed-off-by: Miron Balcerzak <mironbalcerzak@gmail.com>
2019-05-30 20:12:47 +10:00

1.3 KiB

Running Maven Integration tests

The project contains a set of Maven Integration test projects. They are running using the Maven Invoker plugin which starts an external Maven build to run the project and some post build check. More details [http://maven.apache.org/plugins/maven-invoker-plugin/].

Integration tests location

Test projects are located within the folder: src/it

Running the tests

As they can be long to run, the tests do not run per default. So to run them you must activate a profile using the command line argument: -Prun-its

Running single test

You can run single or set of test as well using the command line argument: -Dinvoker.test=it-parent-pom,jetty-run-mojo-it,jetty-run-war*-it,!jetty-run-distro* The parameter supports pattern and exclusion with !

Due to files filtering, it-parent-pom must be included - otherwise tests will fail during execution.

Running Logs

The output of each Maven build will be located in /target/it/${project-name}/build.log

The jetty log output for those goals that fork a new process (currently "distro" and "run-forked") can be found in /target/it/${project-name}/jetty-simple-webapp/target/jetty.out.