skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
naodeng/awesome-qa-skills56 installs

ui-test-cypress

Use this skill when you need to design Cypress e2e and component testing plans with commands, fixtures, network stubbing, and CI reporting; triggers include Cypress UI testing, UI automation testing, and ui-test-cypress.

How do I install this agent skill?

npx skills add https://github.com/naodeng/awesome-qa-skills --skill ui-test-cypress
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill provides a specialized environment for designing and executing Cypress UI tests. It includes mock application fixtures for evaluation and follows security best practices, such as warning against hardcoded secrets and using localized server mocks.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Cypress UI Testing (EN)

Chinese version: See the corresponding Chinese skill.

When to Use

  • Need outputs that should land in a Cypress UI testing workflow.
  • The project already uses Cypress or wants Cypress-ready planning.

Output Format Options

Markdown by default unless the request explicitly asks for another format.

How to Use

  1. Open prompts/ui-test-cypress.md and use it as the main prompt.
  2. Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
  3. If the input is incomplete, return a usable first version and mark missing information and assumptions.

Reference Files

  • When calibrating domain outcomes, valid controls, or evidence gaps, read references/domain-decision-example.md for sanitized input, per-item oracles, and reproducible calculations.

  • prompts/ui-test-cypress.md: main prompt for this skill.

  • references/framework-spec.md: tool-specific structure and coverage notes.

  • references/setup-and-ci.md: setup, execution, and CI notes.

  • examples/sample-context.md: sample request context.

  • scripts/run-tests.sh: lightweight local execution entry point.

Domain Execution Essentials

  1. Read Cypress, Node, browser, config, and component/E2E scope from project artifacts. Generate compatible config, custom commands, specs, and CI commands without implicit upgrades or mixed legacy formats.
  2. Exercise real page/component logic; cy.intercept replaces only confirmed external boundaries. Stub responses alone cannot prove business postconditions. Define isolated fixture data/session cleanup.
  3. Separate retryable queries/assertions, one-time actions, and whole-test retries. Wait on aliased requests/observable states, not sleeps. Preserve first failures and prevent repeated effects.
  4. Use minimum-app positive/negative controls for paid state, amount, and principal. Correct titles with wrong business state must fail assertions and CI. Preserve screenshots/video/failures, teardown, and actual run evidence; files alone prove nothing.

Common Pitfalls

  • Do not use it with vague scope and no context.
  • Do not treat every area as equally important.
  • Do not skip assumptions and missing information.

Best Practices

  • Start from the prompt file, then add only the context that matters.

  • Keep the output risk-driven and executable.

  • If the request is incomplete, return a usable first version and mark gaps.

  • To verify generated business assertions, failure propagation or isolation, read evals/fixtures/checkout-app/README.md and its local good/bug/timeout controls; execute only when a run is requested.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/naodeng/awesome-qa-skills/ui-test-cypress">View ui-test-cypress on skillZs</a>