e2e-testing

Automate end-to-end test setup, writing, and execution with Playwright or Cypress.

105|8|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/686f6c61/alfred-dev --skill e2e-testing-686f6c61
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/686f6c61/alfred-dev/tree/main/skills/calidad/e2e-testing
Command: npx skills add https://github.com/686f6c61/alfred-dev --skill e2e-testing-686f6c61

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation, configuration, and execution of end-to-end tests, ensuring critical user flows function correctly and preventing regressions.

Core Features & Use Cases

  • Tool Selection: Recommends Playwright or Cypress based on project stack.
  • Environment Setup: Guides through configuring test environments, base URLs, and test data.
  • Critical Flow Identification: Helps prioritize testing for essential user journeys like registration, login, and checkout.
  • Test Writing: Adheres to Arrange-Act-Assert patterns with stable selectors.
  • CI Integration: Facilitates setting up E2E tests within CI/CD pipelines.
  • Use Case: Automatically set up Playwright tests for a new e-commerce feature, write tests for the user registration and login flows, and configure them to run on every pull request.

Quick Start

Configure the e2e-testing skill to set up Playwright for the current project and write a test for the user login flow.

Frequently Asked Questions about e2e-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up automated E2E tests for critical user flows?

Automated E2E tests are set up by configuring test environments, base URLs, and test data, then writing tests for critical flows like registration and login using Playwright or Cypress.

What is the best way to integrate E2E testing into a CI/CD pipeline?

Integrating E2E testing into CI/CD pipelines involves configuring automated acceptance tests to run on every pull request, ensuring cross-browser compatibility and preventing regressions in critical user journeys.

How do I write stable E2E tests using Playwright or Cypress?

Writing stable E2E tests requires adhering to the Arrange-Act-Assert pattern and using stable selectors to validate user flows reliably without flakiness across different browser environments.

Should I use Playwright or Cypress for my automated testing framework?

Choosing between Playwright and Cypress for automated testing depends on your specific project stack, as the setup recommends the most suitable tool to validate critical user flows and ensure cross-browser compatibility.

What are the limitations of automating cross-browser E2E tests?

Limitations of automating cross-browser E2E tests involve managing test data stability and environment configurations, requiring strict adherence to best practices to prevent flaky tests during CI integration.