Skip to content
Back to skills

Testing Workflow

ASecurity

Plans tests, writes unit, integration and E2E tests, finds coverage gaps and flags testing anti-patterns. Use when writing or planning tests, mocking dependencies, or checking coverage.

  • 80 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 28, 2026
ai-agentstesting

Security analysis

A100/100

Scanned October 5, 2026

npx -y skills add monkilabs/opencastle --skill testing-workflow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Testing Workflow?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Testing Workflow
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/monkilabs-testing-workflow/badge)](https://www.skillsdirectory.com/skills/monkilabs-testing-workflow)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: testing-workflow
description: "Plans tests, writes unit, integration and E2E tests, finds coverage gaps and flags testing anti-patterns. Use when writing or planning tests, mocking dependencies, or checking coverage."
---

# Testing Workflow

**Mandatory:** test in a real browser via the **e2e-testing** capability slot before marking any feature complete, including every project-defined responsive breakpoint (**validation-gates** Gate 7, **browser-testing** skill).

## E2E Context Limits

| Rule | Detail |
|------|--------|
| One suite per session | never run all suites in one conversation |
| Max 3 screenshots | per session |
| `evaluate_script()` over `take_snapshot()` | returns less data |
| Reload between flows | clears state |
| Report results | in the session output: suite, pass/fail counts, failures with their evidence |

Suite files and project test config: `.opencastle/project.instructions.md`.

## Coverage

| Layer | Minimum |
|-------|---------|
| Unit (functions, components, hooks) | the threshold in the project's test config |
| Integration (boundaries, URL sync) | all boundaries |
| E2E (journeys, interactions, errors) | all critical paths |

Verify with the project's own test and coverage commands (Key Commands in `.opencastle/project.instructions.md`).

## Anti-Patterns

- Testing only initial page load — exercise state/filter changes and confirm results actually differ.
- Assuming a control works because it renders — verify each option changes results and triggers a server request.
- Single scenario — cover empty results, min/max boundaries, invalid input, network errors.
- Visual inspection only — assert data values and URL parameters programmatically.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…