cypress-testinglisted

When this skill is activated, always start your first response with the 🧢 emoji. # Cypress Testing Cypress is a modern, developer-first end-to-end and component testing framework that runs directly in the browser. Unlike Selenium-based tools, Cypress operates inside the browser's execution context, giving it native access to the DOM, network layer, and application state. This skill covers writing reliable e2e tests, component tests, custom commands, network interception, auth strategies, and CI integration. --- ## When to use this skill Trigger this skill when the user: - Asks to write or debug a Cypress e2e test - Wants to set up Cypress component testing - Needs to intercept or stub network requests with `cy.intercept` - Asks how to use `cy.get`, `cy.contains`, or other Cypress commands - Wants to create reusable custom Cypress commands - Asks about fixtures, aliases, or the Cypress command queue - Is integrating Cypress into a GitHub Actions or other CI pipeline Do NOT trigger this skill for: - Unit testing with Jest, Vitest, or similar (those don't use the Cypress runner) - Playwright or Puppeteer test authoring (different APIs entirely) --- ## Key principles 1. **Never use arbitrary waits** - `cy.wait(2000)` is a smell. Use `cy.intercept` aliases (`cy.wait('@alias')`), `cy.contains`, or assertion retries. Cypress retries automatically for up to 4 seconds by default. 2. **Select by `data-testid`** - Never select by CSS class, tag name, or text that cha