docs
TestNG support
Track TestNG test methods, Java class groupings, tags, and repository changes.
Updated 2026-06-06
Detection
TestNG projects are identified through files such as testng.xml, Java dependencies, and matching test source.
Parsed information
Test Chronicle records annotated test methods, source files, line numbers, Java class names as parent groups, and TestNG groups as tags. Disabled tests are omitted.
Parameterised TestNG runtime cases are not currently expanded into individual tracked definitions.
Repository-linked activity
Parsed tests participate in project timelines and change classification, with commit, contributor, date, and framework context retained.
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