Documentation
Set up Test Chronicle, understand the sync model, and reference supported behaviour.
Get started
Create a project, run the first sync, and automate updates.
Getting started with Test Chronicle
Go from an empty account to a populated project using the local sync workflow.
Sync a repository with the local CLI
Use the npm CLI to sync a repository from your own machine before adding CI automation.
Sync with GitHub Actions
Automate incremental project syncs after validating the repository with the local CLI.
Configure projects
Understand automatic behaviour and safely override project-level defaults.
Project configuration
Start with automatic behaviour, then use focused project settings only where your repository needs an override.
Repository defaults
Let the sync agent detect the repository default branch, then optionally choose the primary framework shown first in the dashboard.
Test discovery
Refine where each framework scans for tests while preserving automatic discovery everywhere else.
Testing classification
Control how discovered test files appear in the testing pyramid, filters, and analytics without changing test discovery.
Project areas
Group tests by product, application, service, or package while preserving framework and commit context.
Understand sync and security
See how repository history is processed and what data reaches Test Chronicle.
Frameworks
Check detection and parsed metadata for each supported framework.
Playwright support
Track Playwright test names, files, tags, describe groups, and parameterised patterns.
Cypress support
Track Cypress test names and files, including parameterised patterns.
Vitest support
Track Vitest suites with test names, files, todo markers, and parameterised patterns.
Jest support
Track Jest test names, files, describe groups, todo markers, and parameterised patterns.
pytest support
Track pytest test functions, class groupings, markers, and parameterised decorators.
JUnit support
Track JUnit test methods, Java class groupings, tags, parameterised markers, and repository changes.
TestNG support
Track TestNG test methods, Java class groupings, tags, data-provider markers, and repository changes.
Cucumber support
Track Cucumber scenarios, feature files, tags, and scenario outline examples across repository history.
Reference
Look up change labels and Health Score calculations.