Adam Wisniewski

Notes: 1. The framework for this IT was taken from the LMP's dev mode test 2. The IT project test-liberty-dev-mode is just a shell project with test classes. The test...

Investigate using testcontainers to start databases during integration tests

2

We are currently using the docker-maven-plugin to start containers for db images. This does not work for db2, which does not allow direct pulls from docker hub. The docker-maven-plugin also...

Remove the docker-maven-plugin in the test-jdbc IT and use MicroShed Testing instead. Also need to add a PostgreSQL IT.

The config constants class mostly contains config constants for Liberty. This should be moved to the Liberty runtime adapter and perhaps broken up (i.e. each Liberty booster manages its respective...

Fix test-mpHealth-1.0 IT failure on TomEE

1

The test-mpHealth-1.0 IT is failing on TomEE with the following: The localhost:/health url throws a 404. The URL doesnt seem to exist even when testing manually.

Fix test-dev-release IT failure on TomEE

1

The test-dev-release IT is failing on TomEE with the following: org.apache.openejb.config.UnknownModuleTypeException: Unknown module type: url=/Users/awisniew/Projects/Liberty-Boost/boost/boost-maven/boost-maven-plugin/target/it/test-dev-release/target/it/release-project/target/apache-tomee/apps/ROOT.jar which can't be a war.

There is currently no way to propagate boost properties (like boost.http.port) to integration tests. Typically, integration tests use system properties to read values like server ports, and boost properties are...

**Still to do** (among many things): 1. Change context root from default app name 2. JDBC Booster - flesh out cli commands to add datasource and drivers 3. General cleanup...