L3 - Default Context:
We currently have test dependencies used across the code-base configured per module.
This has a couple of downsides, it's hard to keep them aligned and as test depenencioes are not inherited transitively dependencies have to get duplicated or might trigger compile or runtime errors for tests in maven but not in intellij (as intellij seems to share the classpath across modules).
Even more importantly incorrect dependency setup may lead to tests not being run at all as found on the nightly query performance tests:
[INFO] Running org.camunda.optimize.test.query.performance.QueryPerformanceTest [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 s - in org.camunda.optimize.test.query.performance.QueryPerformanceTest
AT:
- all shared test depenencies are configured in the parent pom.xml
- these are junit
- hamcrest
- assertj
- mockito
- mockserver
- query performance tests run correctly on jenkins