Playwright support

Detection#

Test Chronicle identifies Playwright projects through playwright.config.ts, playwright.config.js, playwright.config.mjs, and related package dependencies. Nested configuration files can identify Playwright projects inside a larger repository.

Automatic detection is usually enough for a standard tests/ or e2e/ layout. In monorepos, use test discovery settings to narrow Playwright scanning to the packages that own browser tests while leaving other frameworks available elsewhere in the same repository.

Parsed information#

Test Chronicle records test names, file paths, line numbers, inline tags, describe groups, and parameterised patterns. Parameterised definitions are marked as patterns; counts represent the definitions found in source rather than every generated runtime case.

Supported patterns include test(), test.describe(), common tag syntax in test titles and annotations, and data-driven definitions that can be identified statically. The recorded source location gives reviewers a stable path back to the Playwright file, even when the runtime output groups tests by project, browser, or retry.

Limits and configuration#

Playwright project matrices, browser projects, and retries are treated as execution detail rather than separate source tests. Test Chronicle focuses on the test definitions that live in Git, so a single source definition remains one tracked item even if Playwright executes it across multiple browsers.

If generated specs, examples, or archived folders are being picked up, add directory exclusions in project settings. If Playwright lives beside Vitest or Jest, framework filters keep the history distinct in the dashboard.

Repository history#

Parsed Playwright tests are compared across Git history to identify additions, deletions, renames, and maintenance changes. The dashboard connects those changes to commits and contributors.

This makes Playwright history useful for release review and test-suite maintenance: teams can see whether browser coverage grew with product work, whether deleted specs were intentional, and which commits explain a visible change in the suite.

Evaluate with the sandbox#

The public Test Chronicle Sandbox combines Playwright and Vitest data and exposes the same summary, timeline, tests, files, contributors, testing-type filters, and Health Score views available to synced projects.