Design spec-based review workflows with visual proof and issue classification. Use when setting up review processes, validating against specifications, or implementing screenshot-based visual validation.
Design optimal test pyramids with unit/integration/E2E ratios. Identify anti-patterns and recommend architecture-specific testing strategies.
Design consumer-driven contract testing strategies using Pact, verify provider contracts, and manage API evolution with contract-first approaches.
Design E2E tests following user-story-driven patterns with verification checkpoints. Use when creating end-to-end tests, validating complete user journeys, or designing Playwright/Cypress test patterns.
Analyze, test, and prepare apps for production with Pest and Playwright testing
Create test cases for functions and modules. Use when implementing TDD or improving coverage.
Run Mojo tests using mojo test command. Use when executing tests or verifying test coverage.
Implement semantic theories and Python/Z3 code with TDD. Invoke for Python-language implementation tasks.
Plan integration tests across modules or services. Use when a mid-level developer needs to verify system interactions.
Design performance test strategies including load profiles, capacity planning, SLA validation, and .NET performance testing with NBomber and k6.
Create comprehensive E2E test plans with deep application analysis, navigation coverage audit, and browser-testable scenarios
Execute complete user flow testing with Playwright MCP, testing end-to-end journeys through the application
Set up test validation commands for any project type. Use when configuring test runners, setting up validation commands for a new project, or enabling closed-loop agent workflows.
Systematically test all pages for errors, functionality, and proper rendering using Playwright MCP
Generate starter unit tests for a small function or module. Use when a junior developer needs test scaffolding and edge cases.
A test skill for validating npm-agentskills functionality
Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.
Apply systematic test case design techniques including equivalence partitioning, boundary value analysis, decision tables, and state transition testing.
Create comprehensive test strategy documents following IEEE 829 structure. Plan test approach, scope, resources, and success criteria for software projects.
Execute comprehensive role-based E2E testing with Playwright, testing all user flows for each role
Set up Pest testing with Orchestra Testbench for Laravel packages
This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Should also be used when editing *_spec.rb files, working in spec/ directory, planning implementation phases that include tests (TDD/RGRC workflow), writing Testing Strategy or Success Criteria sections, discussing unit or integration tests, or reviewing spec output and test failures. Comprehensive RSpec and FactoryBot reference with best practices, ready-to-use patterns, and examples.
Extract and summarize test failures from logs. Use to quickly understand what tests failed and why.
