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.

Go from an empty account to a populated project using the local sync workflow.

Use the npm CLI to sync a repository from your own machine before adding CI automation.

Automate incremental project syncs after validating the repository with the local CLI.

See how repository history is processed and what data reaches Test Chronicle.

Follow the path from a repository checkout to the historical views in the Test Chronicle dashboard.

Review the repository boundary, synced metadata, permissions, credentials, and deletion controls before connecting a project.

Check detection and parsed metadata for each supported framework.

Track Playwright test names, files, tags, describe groups, and parameterised patterns.

Track Cypress test names and files, including parameterised patterns.

Track Vitest suites with test names, files, todo markers, and parameterised patterns.

Track JUnit test methods, Java class groupings, tags, and repository changes.

Track TestNG test methods, Java class groupings, tags, and repository changes.

Track Cucumber scenarios, feature files, tags, and scenario outline examples across repository history.

Look up configuration, change labels, and Health Score calculations.

See which Test Chronicle settings belong in the repository, on the local machine, in the dashboard, and in CI.

Use four consistent labels to interpret test-level activity without losing its Git context.

Understand every factor behind the 0 to 100 project Health Score.