tests-cypresslisted

# Frontend tests: Cypress Cypress can be used for two distinct test types; apply only the sections relevant to the delegation scope. ## E2e tests Write and run frontend e2e specs using Cypress conventions and the repository's frontend test command from crew config. - Spec files live in `cypress/e2e/` (Cypress ≥ 10) or `cypress/integration/` (Cypress < 10). - Use `cy.intercept()` for network stubbing and `cy.fixture()` for test data. - Prefer `data-cy` / `data-testid` selectors over CSS or text selectors for test stability. - **Targeted rerun:** the spec file path, or `--spec`. - **Skip mechanism:** `it.skip`/`describe.skip`, `xit`. ## Component tests Write and run component/unit tests using Cypress Component Testing. The unit-test script is the project's own component-test script, or `npx cypress run --component`. - Component test files live alongside source files or in `cypress/component/`; they use the `.cy.ts` / `.cy.tsx` / `.cy.js` / `.cy.jsx` extension. - Mount components with `cy.mount()` (provided by the framework adapter — e.g. `@cypress/react` or `@cypress/vue`); import and configure the adapter in `cypress/support/component.ts` if not already done. - Use `cy.intercept()` for network stubbing; keep assertions on rendered output, not implementation details. - Prefer `data-cy` / `data-testid` selectors over CSS or text selectors. - **Targeted rerun:** `--spec` in component mode (`--component`).