docs
JUnit support
Track JUnit test methods, Java class groupings, tags, and repository changes.
Updated 2026-06-06
Detection
JUnit detection uses Java build metadata such as pom.xml and relevant package dependencies, together with matching source patterns.
Parsed information
Test Chronicle records annotated test methods, source files, line numbers, Java class names as parent groups, and @Tag values. Tests marked with @Ignore are omitted.
Parameterised JUnit runtime cases are not currently expanded into individual tracked definitions.
History
Supported tests are still mapped to repository commits and classified as additions, deletions, renames, or maintenance changes.
Related reading
Test framework supportTrack multiple JavaScript, Java, and behaviour-driven test frameworks in one project.Project configuration referenceSee which Test Chronicle settings belong in the repository, on the local machine, in the dashboard, and in CI.Test change type referenceUse four consistent labels to interpret test-level activity without losing its Git context.
See it in Test Chronicle
Inspect a populated project or start tracking your own repository history.
Create a free account