Derive high-level test scenarios from a requirement or acceptance criteria before anyone writes detailed steps.
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.
Writes and runs tests (unit, integration, E2E), performs linting, and auto-fixes failures
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 docume — from…
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.
Keep the suite fast enough to run on every change by measuring the slow tests, shaping the pyramid, cutting IO from the fast tier, and sharding.
Test feature branches on Vercel preview deployments using Chrome automation and Gmail OTP
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,…
Comprehensive test strategy design methodology covering risk-based testing, test pyramid optimization, coverage planning, environment strategy, data management, and test…
Designs a risk-based test strategy mapped to acceptance criteria without writing test code unless asked. Use after planning and before or during implementation.
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…
Use when the main question is whether current verification is sufficient for a change, which test layers are missing, and where the smallest high-value regression protection…
Planification de stratégie de test incluant la pyramide de tests, les quadrants de tests, la couverture et l'analyse de risques.
Assess verification scope, regression protection, and risk-based test coverage for changes under review or implementation.
For data structure validation: test lengths, relationships, constraints that must hold, verify setup is correct.
Set up testing infrastructure including framework selection, directory organization, configuration files, and initial test scaffolding. Use when starting a.
Test style rules and the flaky-test red-flag catalog — behavior-not-implementation, DAMP setup, narrow assertions, deterministic-input rules (clock, randomness, ordering, hermetic…
Analyze and score test coverage across all testing dimensions -- unit, integration, E2E, load, visual regression, contract, and accessibility.
Use when when you need to verify that a research software package (e.g., MassQL) maintains functional correctness over time, assess the reliability of a tool before integration…
Optimizing test suite execution speed with parallelization, test splitting, caching, selective test execution, and test impact analysis.
Order and prioritize test suites for faster CI feedback using failure history analysis, code change correlation, coverage-based prioritization, risk-based.
Composite skill — three-phase test quality pipeline. Chains test-health (assess state) → test-cleanup (remove redundant/brittle tests) → mutation-test (validate surviving suite).
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.
QSF project conventions for the Playwright E2E suite. Use when working in the QSF playwright-tests directory (authFixtures, ___ping-* handles, data-test-label test IDs, .auth…
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
Test: Verhandlung, Vergleich und Eskalation: prüft konkret die einschlägigen Tatbestandsmerkmale, Fristen, Belege und Rechtsprechung.
[Tier 2 — Non-Functional: Usability · ISO 25010] Visual regression test workflow — captures baseline screenshots and compares on each run using Playwright snapshots.
Set up Playwright screenshot baselines and CI diffing so UI changes fail pixel-by-pixel instead of by eye.
Run a minimal VoidBox VM smoke test locally. Verifies the VM boots and the LLM responds correctly.
Send WhatsApp messages to other people or search/sync WhatsApp history via the wacli CLI (not for normal user chats). — from kalibr-ai/skills
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.
Develops and tests Laravel packages using Orchestra Testbench. Activates when writing package tests, configuring testbench.yaml, managing migrations, defining routes/environment…
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".
Comprehensive TestCafe end-to-end testing skill for writing reliable browser automation tests in JavaScript and TypeScript without WebDriver dependencies, featuring smart…
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 的 Java 集成测试工作流，用于数据库、中间件和外部依赖的接近真实行为验证。 当任务涉及持久化、消息、缓存、对象存储或多依赖编排时使用。
Testcontainers for Node.js is a library that provides lightweight, throwaway instances of databases, message brokers, browsers, and other services as Docker containers for…
Docker-based integration testing with Testcontainers for databases, message queues, cloud services, and custom containers with lifecycle management.
Teaches the agent to speed up Node integration tests with Testcontainers reuse — withReuse(true), TESTCONTAINERS_REUSE_ENABLE, the .testcontainers.properties opt-in, stable…
Use when the user wants to browse, inspect, create, or update exploratory testing sessions in TestDino — by state, status, session type, assignee, release, or tags.
How TestDriver learns your app and caches what it discovers for instant, deterministic replays
Run TestDriver tests in CI/CD with parallel execution and cross-platform support
The fastest way to get started with TestDriver. Just set your API key and start testing. — from testdriverai/testdriverai
View and analyze saved screenshots using MCP commands for test debugging and development
The fastest way to get started with TestDriver. Just set your API key and start testing. — from testdriverai/testdriverai
Comprehensive testing skill for GabeDA application - designs test strategies (UAT, integration, smoke, unit), creates tests for frontend (React/Playwright) and backend (D — from…