How repository sync works

Detect the project structure

The sync agent scans configuration files, dependencies, and conventional file patterns to identify supported frameworks. Framework directory overrides and exclusions in the Test Chronicle project settings can refine detection for unusual repositories.

Parse the current suite

Framework-specific parsers extract available test names, source files, tags, line numbers, and structural information. The current snapshot is refreshed on each sync so removed files do not remain active.

Walk repository history

On the first sync, the agent processes up to 365 days of Git history. It connects relevant test activity with commit hashes, authors, dates, and messages.

Classify changes

Test activity is recorded as added, deleted, renamed, or maintenance. The exact classification is based on comparisons between the parsed suite and repository history.

Continue incrementally

The service saves the last successfully synced commit hash. Future runs request that marker and process commits that follow it.

History records accumulate while the current test and file snapshot is replaced. Test Chronicle keeps up to 12 months of history visible in the dashboard. Older active records can be archived separately without changing the current suite.