Cypress

The @archibald/cypress package wires Cypress into Archibald projects as the browser end-to-end testing integration. It builds on the shared @archibald/e2e core and ships a ready-made Cypress configuration plus support helpers:

• @archibald/cypress — the config/preset entry consumed by your cypress.config.
• @archibald/cypress/support — support-file helpers (commands, setup) for your spec environment.
• Bundled tooling for TypeScript preprocessing (webpack/babel), code coverage (@cypress/code-coverage) and CI-friendly reporters (JUnit, Mochawesome).

cypress itself is a peer dependency — your project controls the Cypress version.

How to use

archibald add cypress

This scaffolds the cypress/ directory and configures the integration. Import the Archibald support commands in your cypress/support/e2e.ts:

import '@archibald/cypress/support';

Then run the suites through the CLI, which maps your environment/ files onto the Cypress configuration:

archibald e2e --environment local --platform shop

Where the real documentation lives

This page is only a pointer. Usage, configuration, environment handling and selector strategy are documented in the testing guides:

• End-to-end testing — Overview — the shared e2e model (@archibald/e2e), how runners plug in.
• End-to-end testing — Cypress — setup, configuration and usage of this package.
• archibald e2e CLI reference — running the suites.