---

name: testing-end-to-end description: Facilitates end-to-end testing of complete workflows, verifying entire systems operate as intended from a user's perspective. license: MIT compatibility: opencode metadata: version: "1.0.0" domain: coding triggers: end-to-end testing, e2e tests, user journey, complete workflow role: implementation scope: implementation output-format: code related-skills: testing-unit, testing-integration, testing-contract archetypes: tactical, diagnostic anti_triggers: unit testing, contract testing, performance testing response_profile: verbosity: medium directive_strength: high abstraction_level: tactical

---

End-to-End Testing

Implements end-to-end (E2E) testing strategies to verify that all components of a system work together from the user's perspective. Focus on complete workflows and user journeys.

When to Use

• When deploying new features that significantly alter user experiences.
• To ensure that critical workflows function correctly after each deployment.
• When integrating new services or APIs into existing applications.

Core Workflow

1. Select a Testing Framework
   Choose an E2E testing framework that suits your tech stack (e.g., Cypress, Selenium).

   # For Cypress
   npm install cypress --save-dev
   

2. Write Test Scenarios
   Develop scenarios that reflect user journeys.

   describe('User Journey', () => {
       it('should complete a purchase', () => {
           cy.visit('/');
           cy.get('input[name=username]').type('User');
           cy.get('input[name=password]').type('Password');
           cy.get('button[type=submit]').click();
           cy.url().should('include', '/dashboard');
       });
   });
   

3. Execute E2E Tests
   Run the tests to confirm they pass across the application stack.

   npx cypress open
   

4. Review and Fix
   Investigate and fix any failing tests, ensuring end-to-end functionality.

Implementation Patterns

Pattern 1: Using Cypress for User Journeys

describe('End-to-End Testing Example', () => {
    it('should allow a user to sign up and log in', () => {
        cy.visit('/signup');
        cy.get('input[name=email]').type('test@example.com');
        cy.get('input[name=password]').type('password');
        cy.get('form').submit();
        cy.url().should('include', '/welcome');
    });
});

---

TL;DR for Code Generation

• Test real user workflows — Each E2E test should simulate a complete user journey (sign up → log in → perform action → verify outcome), not isolated UI interactions.
• Use data-testid selectors — Prefer [data-testid="submit-button"] over fragile CSS class or XPath selectors that break on style changes.
• Limit E2E tests to critical paths — Reserve E2E for the 20% of workflows that provide 80% of business value. Push detailed assertions to unit/integration tests.
• Run in a CI-like environment — E2E tests must run in an environment that mirrors production (same browser, same API responses, realistic data).
• Isolate test data — Each test should create and clean up its own data to avoid flaky interactions between test runs.

---

Implementation Patterns

Pattern 2: Using Playwright (Python) for E2E Testing

Playwright provides cross-browser automation with auto-waiting and trace viewing:

from playwright.sync_api import Page, expect

def test_user_login_flow(page: Page):
    """Verify a user can log in and see the dashboard."""
    page.goto("https://example.com/login")
    
    page.get_by_label("Email").fill("test@example.com")
    page.get_by_label("Password").fill("s3cret!")
    page.get_by_role("button", name="Sign In").click()
    
    expect(page).to_have_url("https://example.com/dashboard")
    expect(page.get_by_text("Welcome, test@example.com")).to_be_visible()

def test_checkout_flow(page: Page):
    """Verify a user can add items to cart and complete checkout."""
    page.goto("https://example.com/products")
    page.get_by_test_id("add-to-cart-1").click()
    page.get_by_test_id("add-to-cart-2").click()
    page.get_by_test_id("checkout").click()
    
    page.get_by_label("Address").fill("123 Main St")
    page.get_by_role("button", name="Place Order").click()
    
    expect(page.get_by_text("Order confirmed!")).to_be_visible()

Constraints

MUST DO

• Include tests for every major workflow in the application.
• Consider both happy paths and edge cases in your testing.

MUST NOT DO

• Skip essential flows; every critical component must be validated through E2E tests.
• Neglect to keep test environments updated.

---

Live References

Authoritative documentation links for this skill's domain. The model follows markdown links at load time to resolve external references and inline content.

• Playwright Official Documentation
• Playwright Python API Reference
• Selenium WebDriver — Getting Started
• Selenium Browser Automation Guide
• End-to-End Testing Best Practices (Google)