testing-workflow

Plan, execute, and validate unit, integration, and E2E tests for feature releases.

59|12|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/etylsarin/opencastle --skill testing-workflow-etylsarin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-workflow
Source: https://github.com/etylsarin/opencastle/tree/main/src/orchestrator/skills/testing-workflow
Command: npx skills add https://github.com/etylsarin/opencastle --skill testing-workflow-etylsarin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures feature implementations are validated with thorough, repeatable tests and prevents incomplete or visually broken releases by enforcing planning, execution, and verification across unit, integration, and browser E2E tests. It also mitigates AI context overflow during browser-driven E2E runs by prescribing session limits and data-minimizing rules.

Core Features & Use Cases

  • Pre-implementation Test Plans: Create initial state, interaction, transition, edge case, integration, and responsive breakpoint tests before coding starts.
  • E2E Context Management: Rules for one suite per session, max three screenshots, prefer evaluate_script() over large snapshots, and reloads between major flows to avoid context exhaustion.
  • Coverage & Validation Gates: Enforces minimum coverage for new code, mandatory responsive breakpoint checks, and documented post-implementation browser test results.
  • Use Case: Use when implementing a new UI feature to generate a detailed test plan, run targeted E2E checks in the browser, and record verification artifacts for release gates.

Quick Start

Use the testing-workflow skill to produce a pre-implementation test plan, required coverage thresholds, and a browser E2E checklist for the new feature.

Frequently Asked Questions about testing-workflow

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

FAQPage Schema
How do I create a pre-implementation test plan for a new UI feature?

To create a pre-implementation test plan, define initial state, interaction, transition, edge case, integration, and responsive breakpoint tests before coding starts to ensure comprehensive feature validation.

How do I prevent context overflow during browser E2E test automation?

Prevent context overflow during browser E2E tests by enforcing one suite per session, limiting to three screenshots, preferring evaluate_script() over large snapshots, and reloading between major flows.

What coverage thresholds and validation gates are required for feature releases?

Feature releases require minimum coverage for new code, mandatory responsive breakpoint checks, and documented post-implementation browser E2E test results to pass validation gates.

How do I validate unit, integration, and E2E tests for a feature release?

Validate feature releases by planning, executing, and verifying unit, integration, and browser E2E tests to prevent incomplete or visually broken releases through repeatable test workflows.

Why should I use a structured testing workflow for web UI development?

Use a structured testing workflow for web UI development to enforce per-feature test plans, mandatory browser verification, coverage minimums, and session management rules that prevent visually broken releases and context exhaustion.