Test framework support

Supported frameworks#

Test Chronicle detects and parses Playwright, Cypress, Vitest, Jest, pytest, JUnit, TestNG, and Cucumber projects. A repository can contain more than one supported framework; detected suites are recorded independently while remaining visible in the same project.

Core support includes test names and source files. Tags, class or describe-block structure, and parameterised patterns vary by framework because each ecosystem represents tests differently.

Framework-specific test history matters because a browser suite, a unit-test suite, and a behaviour-driven suite often change for different reasons. Keeping those frameworks labelled helps teams distinguish product coverage, fast feedback tests, and migration activity in the same repository.

Automatic detection with project overrides#

The sync agent looks for framework configuration, dependencies, and conventional file patterns. Teams with non-standard layouts can set framework directories and directory exclusions in the Test Chronicle project settings.

The local testchronicle.config.json file only connects a repository checkout to its Test Chronicle project.

Use automatic detection first, then add overrides only when generated files, examples, archived folders, or monorepo boundaries make the result too broad. The test discovery reference documents how to narrow a framework without losing the rest of the project.

Framework-aware views#

Recorded framework data can be used to filter timelines, tests, files, and project trends. This matters for monorepos and migration periods where several test systems may coexist.

Use the framework documentation to check the current detection method and supported metadata for a repository.

During migrations, framework filters make test history easier to read. A team can see Jest activity shrink while Vitest grows, or Playwright coverage expand while unit-test maintenance stays steady.