Writes Cypress E2E/component tests, configures `cy.intercept()` and `cy.session()`, authors custom commands, and wires CI artifacts. Use when creating E2E specs, component tests, or CI test pipelines. Trigger terms: cypress, e2e, component test, cy.intercept, cy.session
72
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Project test config and breakpoints: testing-config.md. Docs: https://docs.cypress.io
Specs cypress/e2e/ • fixtures cypress/fixtures/ • custom commands cypress/support/commands.ts • failure artifacts cypress/screenshots/ and cypress/videos/.
cy.session(key, setupFn) caches and restores auth state across specs — the cache key must include every credential that changes the session, or you will silently reuse the wrong user.@alias names for cy.intercept() routes. Shared alias names cause cross-test cy.wait() collisions when specs run in parallel.cy.intercept() with fixed fixture payloads over seeding real data — it is the only reliable fix for network flake.data-testid → aria-* / role. Never auto-generated classes or deep CSS paths.npm install --save-dev cypress, run npx cypress verify — a corrupted binary cache fails later with confusing errors.npx cypress open # interactive
npx cypress run # headless / CI, assert exit 0
npx cypress run --spec "cypress/e2e/auth/login.cy.ts" --headed # single-spec smoke checkOn failure, re-run the failing spec alone and inspect the screenshot/video artifacts. In CI, upload those artifacts only on failure.
fa0c341
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.