Menu
[Testing] Test plans from E2E scenario catalog (105 scenarios, 18 domains). Maps to regression suites.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
[Testing] Review test cases for quality, determinism, completeness, data validity, coverage gaps, duplication, live environment verification, and behavioral triangulation against docs + live + source. Delegates browser verification to qa-testing-expert; triangulation to ba-system-analyzer.
[Testing] Postman MCP collections — create, configure, verify, and export collections with proper variables, auth, and endpoints
[Testing] Autonomous test coverage gap analysis and generation — identifies missing test cases, generates enriched CSV test cases, validates P0 cases via browser, and reports improvements. Single-agent counterpart to /qa-coverage-generation.
Repo/tracker routing library for the vc-fix plugin — decides which external product repo owns a bug (client vs platform), whether the fix delivers as a direct PR, a fork-PR, or an upstream issue, and which VCS/tracker host to talk to. Used by /qa-fix and /project-init. Self-contained — no dependency on the ci/ directory.
Build, launch, smoke-test, and health-check the vc-mcp-testing-module agentic QA tooling repo. Use when asked to run, start, verify, smoke-test, or sanity-check this repo's tooling — env:check, @td() resolution, suite manifest sync, critical-UI-scope, seed dry-run, GraphQL fixture validation — or before running regression.
[QA Methodology] Triage a completed regression run's failures: collect each FAIL + its evidence (trace, screenshots, console, network) + failing CSV row, dedup + flag flaky, classify each into real-product-bug vs test-defect (bad steps / bad assertion / stale test data / stale test) vs flaky/env/known, live-verify the real ones, then route test-defects to /qa-review-tests --fix and draft bug reports. Detect-classify-verify-report only — never files a tracker ticket, never triggers /qa-fix.
| name | qa-plan |
| description | [Testing] Test plans from E2E scenario catalog (105 scenarios, 18 domains). Maps to regression suites. |
| argument-hint | feature name | domain | VCST-XXXX |
| disable-model-invocation | true |
Create test plans and detailed test cases using the comprehensive E2E scenario catalog. Maps features to business domains and regression suites.
/qa-plan checkout # Test plan for checkout domain
/qa-plan VCST-1234 # Test plan for a JIRA ticket
/qa-plan authentication # Test plan for auth domain
/qa-plan "configurable products" # Test plan for configurable products
Identify affected domains:
Delegate to test-management-specialist via Task tool (subagent_type: test-management-specialist):
e2e-scenario-catalog.md for relevant scenariosFor each domain, generate:
Output format:
reports/tickets/SprintXX-XX/VCST-XXXX/
├── test-plan.md
├── test-cases.md (or test-cases.csv)
└── testrail-import.csv
Summary to user:
| # | Domain | Prefix | Scenarios |
|---|---|---|---|
| 1 | Authentication & Registration | E2E-AUTH | 8 |
| 2 | Catalog & Product Discovery | E2E-CAT | 8 |
| 3 | Search | E2E-SEARCH | 5 |
| 4 | Cart | E2E-CART | 7 |
| 5 | Checkout | E2E-CHECKOUT | 6 |
| 6 | Payment | E2E-PAY | 6 |
| 7 | BOPIS | E2E-BOPIS | 5 |
| 8 | B2B Features | E2E-B2B | 7 |
| 9 | Orders & History | E2E-ORDER | 6 |
| 10 | Inventory | E2E-INV | 5 |
| 11-18 | Marketing, CMS, Notifications, Settings, Import/Export, SEO, Analytics, Security | Various | 42 |
/qa-test/qa-test (Steps 2–3) reuses this skill's e2e-scenario-catalog.md for E2E-* scenario coverage + regression-suite traceability, but produces only its scoped testing-checklist.md — not the full test plan / RTM / TestRail CSV this skill generates. Full case authoring + the peer-review Draft → Reviewed promotion gate belong to a standalone /qa-plan run, never to a /qa-test verdict pass.