Cypress support

Detection

Test Chronicle detects Cypress through cypress.config.ts, cypress.config.js, cypress.json, package dependencies, and conventional test locations. Where available, the configured specPattern helps identify the relevant files.

Parsed information

Test Chronicle records test names, file paths, describe groups, line numbers, and common forEach parameterised patterns. Cypress tags are not currently recorded as a supported metadata field.

History views

After parsing, test changes are mapped to Git commits and appear in the same timeline, test, file, contributor, and trend views used by other frameworks.

For repositories with a custom Cypress layout, set an explicit Cypress directory in the Test Chronicle project settings.