Home

Running integration tests

They can take minutes to run, so are disabled by default.

Basic execution:

mvn install

To run with all integration tests:

mvn install -Pit

To run only some integration tests (e.g. one module):

mvn install -Pit -Dinvoker.test=test-jaxrs*

To run with integration tests on a preset runtime:

Use runtime=ol for io.openliberty:openliberty runtime or runtime=wlp for com.ibm.websphere.appserver.runtime:wlp-javaee7. Set the runtime version using the runtimeVersion property. For example, to test on Open Liberty 18.0.0.3, use:

mvn install -Pit -Druntime=ol -DruntimeVersion=18.0.0.2

To run with integration tests on a specific runtime:

Set the runtimeGroupId, runtimeArtifactId, and runtimeVersion properties. For example, to test on Open Liberty 18.0.0.3, use:

mvn install -Pit -DruntimeGroupId=io.openliberty -DruntimeArtifactId=openliberty-runtime -DruntimeVersion=18.0.0.3

To run against a remote Docker engine:

export DOCKER_HOST=tcp://myhost.com:2375; mvn install -Pit ...

Eclipse

When importing the code into Eclipse, do it in two steps:

1. Import the top-level project

Import -> Maven (Existing Maven Projects)

"Root Directory" => repo home (project.basedir)

2. Import the parent of the individual integration test projects

Import -> Maven (Existing Maven Projects)

"Root Directory" => IT parent module home (project.basedir/src/it)

Troubleshooting

ITs (and Boost package) runs slow on Windows 10

Windows Defender can greatly slow down the unzip of a Liberty runtime performed in the package goal, currently from about 10s -> 80s.

Solution: Follow steps like these to take a subdirectory and remove it from scanning.