Showing 30 of 27339 results
Generate reviewer-ready test cases from Jira tickets using Jira MCP. Use when a Jira issue, story, or epic needs coverage drafted for user review.
k6-specific best practices for performance tests, including load, stress, spike, and soak testing. Use when writing or reviewing k6 performance tests.
Orchestrate complex test workflows with dependencies, parallel execution, and smart test selection
Pact-specific best practices for consumer and provider contract tests. Use when writing, reviewing, or refactoring Pact tests.
Playwright-specific best practices for reliable, parallel-safe end-to-end tests. Use when writing or reviewing Playwright tests.
Postman-specific best practices for API tests: collections, environments, pm.* assertions, Newman, and CI. Use when writing or reviewing Postman API tests.
Refactor automated tests to improve maintainability, readability, and organization without changing behaviour. Detects the framework used and applies the matching framework's refactoring patterns.
Generate comprehensive test reports with coverage, trends, and stakeholder-friendly formats
Analyze test failures, identify patterns, and suggest targeted fixes
Review automated tests against core and framework-specific testing standards. Diagnoses issues and produces a verdict; recommends test-refactor for structural changes. Detects the framework used and applies the matching framework's review patterns.
Run tests with coverage and baseline tracking (pytest, with JS/TS support planned)
Parallel test runner for comprehensive Python quality checks (pytest, ruff, mypy, bandit) with faster execution
Core discipline for unit tests across frameworks: Arrange-Act-Assert structure, behaviour-focused naming, isolation, mocking discipline, and meaningful coverage. Use when writing, reviewing, or maintaining unit tests.
Vision-driven e2e test suite generation. /test-vision for full repo analysis + parallel test suite creation. /e2e for single-feature spec generation. Composes /e2e as the atomic unit within /test-vision orchestration.
Vitest-specific conventions for unit tests: test doubles, fake timers, async assertions, parametrisation, and config. Use when writing or reviewing Vitest tests.
WebdriverIO-specific best practices for stable and maintainable tests. Use when writing or reviewing WebdriverIO tests.
Write tests that verify behavior (not implementation), use table-driven/parameterized patterns, and minimize mocking. Supports Go, Python, TypeScript, Java, and Rust.
Generate comprehensive unit and integration tests with full coverage
Testany ๆต่ฏๅนณๅฐๆบ่ฝๅฉๆ๏ผ้็จ็๏ผ๏ผplatform case ็ผๅไธๆณจๅใpipeline ็ผๆใtrigger ้ ็ฝฎใexecution ็ฎก็ใๆ ้่ฏๆญใๅ ผๅฎน VS Code CopilotใGitHub Copilot ็ญๅนณๅฐใๅฝไปค๏ผ/testany-bot:case, /testany-bot:case-writing, /testany-bot:pipeline, /testany-bot:execution, /testany-bot:debug, /testany-bot:trigger, /testany-bot:workspace
AI/LLM ๅทฅๅ ท้๏ผPrompt ไผๅใๅฝไปค๏ผ/testany-llm:prompt-optimizer
Use TestDino inside Claude Code through the hosted remote MCP server to inspect test runs, debug failing test cases, manage manual tests, and run TestDino audits.
Skills for verifying that tests actually test something: a dependency-free harness for unit-testing Workflow scripts, mutation-verification for renderer tests, real-browser checks for Streamlit UIs, and zsh traps that fake out verification blocks.
Test-suite hygiene and generation toolkit - binding test-hygiene rules (search-before-write protocol, mirror-the-source placement, deterministic ownership per layer, explicit layers with budgets, no skip markers, assertion integrity, delete tests with the feature), a report-only test-suite-auditor agent (orphan, skipped, failing, flaky, duplicate, contradictory, implementation-coupled and never-failing test detection plus layer and runtime/coverage distribution), /test-audit with a versioned TEST_AUDIT.md and gated quarantine to tests/_quarantine/, /test-consolidate with behavior-inventory approval, same-commit rewrite plus delete and a coverage gate, and a test-writer agent that generates behavior-driven test suites and extends existing test files instead of creating parallel ones. TDD methodology and browser E2E patterns are delegated to hard dependencies: mattpocock-skills (tdd) and developer-essentials (e2e-testing-patterns)
Test-suite hygiene and generation toolkit - binding test-hygiene rules (search-before-write protocol, mirror-the-source placement, deterministic ownership per layer, explicit layers with budgets, no skip markers, assertion integrity, delete tests with the feature), a report-only test-suite-auditor agent (orphan, skipped, failing, flaky, duplicate, contradictory, implementation-coupled and never-failing test detection plus layer and runtime/coverage distribution), /test-audit with a versioned TEST_AUDIT.md and gated quarantine to tests/_quarantine/, /test-consolidate with behavior-inventory approval, same-commit rewrite plus delete and a coverage gate, and a test-writer agent that generates behavior-driven test suites and extends existing test files instead of creating parallel ones. TDD methodology and browser E2E patterns are delegated to hard dependencies: mattpocock-skills (tdd) and developer-essentials (e2e-testing-patterns)