See How Your Tests EvolveWith Your Code
Track test additions, deletions, renames, and maintenance changes over time with git-mapped history. Get visibility into test evolution, spot quality trends, and surface coverage gaps across your team.
Simple, Fair Pricing
Start free. Upgrade only when your test suite grows. No credit card required.
Sandbox
Try without committing
- ✓Demo projects included
- ✓Full feature access
- ✓No signup needed
- ✓Sample test data
- ✗Create projects
Free
Try it with your own project
- ✓1 project
- ✓Unlimited history
- ✓All visualisation tools
- ✓Search & filters
- ✗Team collaboration
Team
Introduce it to your team
- ✓Up to 20 projects
- ✓Unlimited history
- ✓All visualisation tools
- ✓Unlimited team members
- ✓Role-based access control
- ✓Team project sharing & collaboration
Complete Test Suite Visibility
For QAs, developers, and management
Test Evolution Timeline
Interactive timelines and dashboards showing test additions, deletions, renames, and maintenance changes mapped to your git history.
Quality Trend Analysis
Surface trends in test coverage additions across features and identify gaps in quality coverage to strengthen your test suite.
Smart Sync
One-command setup. Auto-detects frameworks. Incremental syncs mean fast, efficient tracking.
Advanced Filtering
Filter by author, type, tags, or test. Find exactly what you're looking for.
Test Activity & Evolution
Track test activity over time with full git history context. Understand how quality strategy evolves alongside your codebase.
Collaborative Quality Visibility
Give QAs, developers, and management a clear picture of test suite development. Share quality insights and responsibility across teams.
Built for Your Stack
Works with the frameworks your team already uses
| Framework | Test Names | Spec Files | Tags | Param Detection* |
|---|---|---|---|---|
 Playwright | ||||
 Cypress | ||||
 Vitest | ||||
 TestNG | ||||
 JUnit | ||||
 Cucumber |
* Parameterized patterns are detected and flagged — test counts reflect definitions, not individual runs.
What Your Test Activity Is Telling You
Every commit tells a story. Test Chronicle surfaces four signals that reveal the health and momentum of your test suite at a glance.
Added
Your team is building coverage
New tests appear when features ship or coverage gaps are plugged. A healthy project shows a steady stream of additions over time, meaning testing is happening alongside development, not as an afterthought.
Deleted
Features have changed or retired
Deleted tests are a normal part of a living codebase. Features get removed, flows change, redundant tests get cleaned up. Spikes in deletions alongside few additions can be an early signal that coverage is thinning in a specific area.
Renamed
Tests are keeping pace with your product
When a feature evolves in name or scope, a good team updates the test to match. Renames indicate that tests aren't being left behind with stale descriptions, so your test suite reflects what the product actually does today.
Maintenance
Your tests are being actively owned
Maintenance marks appear when the intent of a test stays the same but the implementation changes: selectors updated, assertions tightened, setup adjusted. These are a positive signal that someone is keeping the test accurate as the codebase shifts, not just letting it pass quietly while going stale.
Ready to improve your test quality?
Start free with the Sandbox demo or create your free account