playbooks

home / skills / git-fg / thecattoolkit / testing-e2e

testing-e2e skill

/plugins/sys-browser/skills/testing-e2e

This skill orchestrates end-to-end testing workflows by coordinating server setup, browser automation, and result analysis for complete user flows.

npx playbooks add skill git-fg/thecattoolkit --skill testing-e2e

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.5 KB
---
name: testing-e2e
description: "Orchestrates end-to-end testing workflows coordinating browser automation with server verification. Use when validating complete user flows, testing multi-step scenarios, or verifying browser-server integration. Do not use for unit testing, API testing, isolated component testing, or documentation code examples → see generating-tests skill."
context: fork  # Required: Coordinates browser automation with server-side verification, orchestrates complete test workflows
user-invocable: false
allowed-tools: [Read, Write, Edit, Glob, Grep, Bash, Task]
---

# End-to-End Testing Orchestration



## Test Workflow

### 1. Test Planning
- Identify user flows to validate
- Define success criteria
- Map test scenarios to requirements

### 2. Environment Setup
- Start server (if needed)
- Configure browser automation
- Prepare test data

### 3. Test Execution
- Run browser automation steps
- Verify server responses
- Capture screenshots/logs on failure

### 4. Results Analysis
- Compare actual vs expected outcomes
- Generate test reports
- Identify failures and root causes



## Orchestration Pattern

1. **Coordinate**: Start server, launch browser
2. **Execute**: Run test steps in sequence
3. **Verify**: Check server state, browser output
4. **Report**: Consolidate results and findings

## Reference Materials

Test patterns and verification strategies are documented inline above.

**Note**: For isolated browser automation, use `driving-browser` skill. For server-only testing, use appropriate backend testing tools.

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

FAQ

Can I use this for unit or API-only tests?

No. This skill targets integrated end-to-end scenarios. Use unit testing frameworks for isolated logic and API-only tools for backend endpoints.

What happens on test failures?

The orchestration captures screenshots, browser logs, and server traces, then includes these artifacts in the consolidated report to speed diagnosis.