Unit tests
Unit tests run on JUnit 5 through Surefire, as part of every ./mvnw clean install.
./mvnw test -pl core # one module
./mvnw test -pl core -Dtest=ConstTest # one classWhat you get for free
The Surefire configuration in the root pom points HOP_AUDIT_FOLDER at the module’s target/, so tests never write into a developer’s real audit folder.
hop-core, hop-engine and hop-ui publish test jars, and the plugins parent already puts them on every plugin’s test classpath, so a plugin test can reuse the shared fixtures without adding a dependency. org.apache.hop.core.util.TestUtil registers the built-in value types, a database plugin and a password encoder, which is enough for a test that only needs to construct rows.
Most tests that touch anything plugin-based need an initialised environment. HopClientEnvironment.init() is enough for value types, databases and metadata; HopEnvironment.init() is needed as soon as transforms or actions are involved.
A trap worth knowing
-Dtest=!SomeTest silently discards the Surefire excludes configured in the module poms, so a full-reactor run with that flag can surface a large number of failures that are not real. Exclude by editing the pom, or run the module on its own.
| This page is a scaffold. Still to write:
|