testing-e2e_skill

Overview

This skill orchestrates end-to-end testing workflows by coordinating browser automation with server-side verification. It validates complete user flows, multi-step scenarios, and browser-server integration to ensure real-world behavior matches requirements. Use it to run integrated tests that exercise the full stack from UI interactions to backend state changes.

How this skill works

The skill starts by preparing the environment: launching the server, configuring the browser automation driver, and seeding test data. It executes scripted browser steps in sequence while concurrently checking server responses and state changes. On failures it captures screenshots, logs, and traces, then consolidates results into human- and machine-readable reports for analysis.

When to use it

• Validating complete user journeys that span UI and backend
• Testing multi-step scenarios with persistent server state
• Verifying browser-server interaction and side effects
• Running smoke or regression tests against integrated environments
• Capturing reproducible failure artifacts (screenshots, logs)

Best practices

• Design tests around concrete user flows and clear success criteria
• Keep environment setup reproducible: use fixtures, seed data, and containerized services
• Isolate flaky steps with retries and deterministic waits rather than fixed sleeps
• Collect screenshots and server logs on failure for fast triage
• Limit test scope per scenario to reduce brittle, slow end-to-end suites

Example use cases

• Registering a new user through the UI, confirming email flow, and verifying DB entry
• Completing a checkout flow: add to cart, payment, order confirmation, and server invoice
• Testing SSO login: redirect handling in browser plus token validation on server
• Verifying feature flags: toggle on backend and confirm UI exposure and state changes
• Running nightly regression tests to detect integration regressions across services