← LeaderboardThe Skill Leaderboard

e2e-testing-patterns

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

Description awaits a fresh source check.

Published by rmyndharis ↗rmyndharis/antigravity-skills

Try your first task

Plan One Safe E2E Test

Start a fresh conversation. Replace the highlighted placeholders.

Use the e2e-testing-patterns skill to design one small, non-destructive end-to-end test for [critical user journey] using the project's existing Playwright or Cypress setup. Define the success criteria, stable selectors, isolated test data, retry and tracing behavior, and how the test should run in CI. Do not target production.

Required inputs

  • Critical user journey
  • Existing test framework or preference
  • Safe test environment
  • Dedicated test-data or test-account details

Previously published starter task based on a pinned source version; check the source and required inputs before running. Task evidence ↗

SKILL.md

name: e2e-testing-patternsdescription: Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

E2E Testing Patterns

Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do.

Use this skill when

  • Implementing end-to-end test automation
  • Debugging flaky or unreliable tests
  • Testing critical user workflows
  • Setting up CI/CD test pipelines
  • Testing across multiple browsers
  • Validating accessibility requirements
  • Testing responsive designs
  • Establishing E2E testing standards

Do not use this skill when

  • You only need unit or integration tests
  • The environment cannot support stable UI automation
  • You cannot provision safe test accounts or data

Instructions

  1. Identify critical user journeys and success criteria.
  2. Build stable selectors and test data strategies.
  3. Implement tests with retries, tracing, and isolation.
  4. Run in CI with parallelization and artifact capture.

Safety

  • Avoid running destructive tests against production.
  • Use dedicated test data and scrub sensitive output.

Resources

  • resources/implementation-playbook.md for detailed E2E patterns and templates.
e2e-testing-patterns by rmyndharis · The Skill Leaderboard