Test suite history

Make test history easier to read

Git contains the history of a test suite, but it is organised around files and lines. Test Chronicle builds a test-focused view that connects parsed tests and files to commits, authors, dates, and frameworks.

The timeline and filters help answer:

• What changed in the tests around a release?
• Was a test added, deleted, renamed, or maintained?
• Which files or tests change repeatedly?
• Who contributed to the suite during a selected period?

Classify changes without losing context

Test Chronicle records four change types:

• Added: a new test appears.
• Deleted: a recorded test no longer appears.
• Renamed: a test is matched across a name change.
• Maintenance: an existing test changes while remaining in the suite.

These labels make activity easier to scan while retaining the affected test, file, commit, author, date, and framework.

Change volume is not automatically good or bad. A refactor can produce legitimate renames, while removing obsolete behavior can correctly delete tests. Patterns become useful when they are reviewed over releases or sprints and traced back to their commits.

Keep Git as the evidence

Test Chronicle does not replace source control or code review. It provides a shorter route from a test-suite signal to the repository evidence needed to understand it.