Improve integration Test environment initialization
@MikeNeilson is already working on this.
Since Nov 20, 2025.
- Dominant language
- Java
- Stars
- 28
- Forks
- 25
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 20
Description
During #1474 it was attempted to dynamically discover the database version from the database to render as the displayname. However, due to the order of operations (the CdaSetupCallbackExtension doesn't run before test discovery) this fails.
After a search of junit lifecycle operations there is a LauncherSessionListener available https://docs.junit.org/current/api/org.junit.platform.launcher/org/junit/platform/launcher/LauncherSessionListener.html
This runs before test discovery and actual startup/other initialization settings should be handle here.
The current extension, if it works out, will be expanded to implement the launcher session listener to start the database. Will also include appropriate renentrant locks, it would be nice to run these tests in parallel, the time to finish is getting rediculous.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.