[Tier 3 — Non-Functional: Performance Efficiency · ISO 25010] Soak test workflow — sustained load for 30-60 min to detect memory leaks and connection pool exhaustion.
[Tier 3 — Non-Functional: Performance Efficiency · ISO 25010] Stress test workflow — ramps load beyond capacity to find breaking point and verify recovery.
Use when optimizing test suite performance — database setup, seeder optimization, parallel testing, CI pipeline efficiency, or RefreshDatabase alternatives.
Test plan generation skill covering requirements analysis, test strategy, coverage matrices, risk-based testing, and test estimation techniques.
Close the PDCA loop on the work you just did. After implementing changes, drive the LIVE app on localhost through the Playwright browser MCP like a real end user — manually, not…
Use to restructure code while guaranteeing that all existing tests continue to pass.
Use when creating or editing any prompt (commands, hooks, skills, subagent instructions) to verify it produces desired behavior - applies RED-GREEN-REFACTOR cycle to prompt…
GENERIC webapp QA fallback — use ONLY when no project-specific QA skill applies (66ai-user-story-testing for 6-6 AI, sbc-qa-data-integrity-audit/sbc-pdca-audit for 一人社長,…
Analyze test code quality to detect coverage-only tests, test smells, and low-value assertions. Use when asked to "analyze test quality", "find coverage-only tests", "audit our…
Pre-test readiness workflow that finds and fixes predictable validation blockers before running expensive local or container test gates.
Validate that reasoning parameters are correctly serialized and sent to provider APIs. Use when the user asks to test reasoning serialization, run reasoning tests, verify…
When renaming a function, test files have references that survive find-and-replace:
Test Retry Config - Auto-activating skill for Test Automation. Triggers on: test retry config, test retry config Part of the Test Automation skill category.
Use when auditing tests that may not verify real behavior: tautological assertions, missing assertions, skipped tests without a tracker, mock-everything tests, swallowed…
Run plugin test suites in this monorepo and report a concise pass/fail summary. Optional plugin slug arg; without arg, runs all plugins under plugins/.
Auto-detect and run project tests — supports Go, TypeScript, Python, Rust, and more
Generate test file scaffolds from source analysis with language-appropriate templates.
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.
Use when writing RSpec tests for service objects, API clients, orchestrators, or business logic in spec/services/.
BATS shell script testing. Use when writing or running shell script tests. Covers setup/teardown, assertions, mocking, helper patterns, and coverage with kcov.
Test Shiny applications using shinytest2 for end-to-end browser tests and testServer() for unit-testing module server logic.
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation…
Deep formal test smell audit based on academic research taxonomy (testsmells.org). Detects 19 categorized smell types — conditional logic, mystery guests, sensitive equal — from…
Generates comprehensive test specification with unit tests, UI tests, accessibility testing, and beta testing plan. Creates TEST_SPEC.md from PRD and implementation specs.
Testing strategy and design - what to test, how to test, and when testing is overkill. From TDD to integration tests to knowing when to skip tests entirelyUse when "test, testing,…
Write a test strategy document from a feature spec, PRD, or system description. Use when asked to create a test plan, write a test strategy, define QA approach, or plan testing…
Planification de stratégie de test incluant la pyramide de tests, les quadrants de tests, la couverture et l'analyse de risques.
For data structure validation: test lengths, relationships, constraints that must hold, verify setup is correct.
Analyze and score test coverage across all testing dimensions -- unit, integration, E2E, load, visual regression, contract, and accessibility.
Detect orphaned tests, obsolete assertions, and test-code misalignment. Use for test suite maintenance, cleanup, and traceability validation.
Analyzes test suites and tags each test with a standardized set of traits (e.g., positive, negative, critical-path, boundary, smoke, regression).
Execute a test scenario against a team, observing coordination pattern behaviors, evaluating acceptance criteria, and generating a structured RESULT.md.
Use before scaling any message, after a launch underperforms, or whenever positioning is still a hypothesis (pre-users).
Use when a verdict rests on a measured quantity rather than a single deterministic assertion — a noisy/probabilistic output, a performance number, an accuracy or conversion rate.
Triage failing macOS tests across Xcode and SwiftPM workflows. Use when asked to run macOS tests, narrow failing scopes, explain assertion or crash failures, or separate — from…
Playwright E2E testing best practices. Use when writing browser tests, visual regression, or accessibility tests.
Patterns and conventions for writing *.test.ts files in this project. Load when creating or editing unit test files.
Update, generate, and validate tests using git-workspace-review for change context
[Tier 2 — Non-Functional: Usability · ISO 25010] Visual regression test workflow — captures baseline screenshots and compares on each run using Playwright snapshots.
Run a minimal VoidBox VM smoke test locally. Verifies the VM boots and the LLM responds correctly.
For example-driven development: test cases as specifications, input/output pairs, documentation through examples.
Use when backfilling tests on existing code. Analyzes code through public interfaces, detects the project's test framework, and writes behavior-focused regression tests.
Write comprehensive tests for code including unit tests, integration tests, and end-to-end tests. Use this to ensure code quality, catch bugs, and validate functionality.
TestCafe is a Node.js-based end-to-end browser testing framework by DevExpress that requires no WebDriver installation.
Generates TestCafe automation tests in JavaScript or TypeScript. Supports local and TestMu AI cloud. Triggers on: "TestCafe", "test cafe", "fixture/test".
Write integration tests using TestContainers for .NET with xUnit. Covers infrastructure testing with real databases, message queues, and caches in Docker containers instead of…
Testcontainers for Node.js is a library that provides lightweight, throwaway instances of databases, message brokers, browsers, and other services as Docker containers for…
Comprehensive testing skill for GabeDA application - designs test strategies (UAT, integration, smoke, unit), creates tests for frontend (React/Playwright) and backend (D — from…
Comprehensive testing skill for GabeDA application - designs test strategies (UAT, integration, smoke, unit), creates tests for frontend (React/Playwright) and backend (D — from…
Comprehensive testing strategies for Guts including unit tests, integration tests, property-based testing, and fuzzing — from AbdelStark/guts
Comprehensive testing strategies for Guts including unit tests, integration tests, property-based testing, and fuzzing — from bg-szy/TOP-SKILLS
Expert at Playwright E2E tests, Vitest unit tests, Storybook interaction tests. Use when writing tests, debugging test failures, or improving test coverage.
Advanced testing: E2E with Playwright/Cypress, property-based testing, mutation testing, contract testing, and CI/CD pipelines.
Use when designing tests, implementing test cases, running tests, analyzing test coverage, or fixing test failures.
Write, run, and analyze structured test suites for Agentforce agents. TRIGGER when: user writes or modifies test spec YAML (AiEvaluationDefinition); runs sf agent test create,…
Run OceanBase performance benchmarks and functional tests using obd test. Supports Sysbench, TPC-H, TPC-C benchmarks and mysqltest functional tests.
Testing conventions, CI pipeline rules, and smoke test coverage for SkillHub. Ensures agents write tests correctly and understand the CI gate requirements.
Use when: creating or improving test strategy, unit/integration/e2e coverage, load testing, and quality gates for InfraNexus backend/frontend.
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
Tests API authentication mechanisms for weaknesses including broken token validation, missing authentication