Menü
[Testing] Test plans from E2E scenario catalog (105 scenarios, 18 domains). Maps to regression suites.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Initialize / onboard this agentic-QA plugin onto a deployment. Installs deps, then asks the operator only what genuinely shapes the config — the environment NAME, the bug tracker (Jira / Azure Boards), the code host (GitHub / Azure Repos), and an auth preference per axis (PAT recommended, else browser/CLI login). Everything else — whether it is a native-platform or a CLIENT project, the client org, the contribution mode, the fork account — is DERIVED from the token + the filled env + a live module/repo scan. Writes project-profile.json + .env.<env> + .env.local + .mcp.json and verifies access. The whole point is to make /qa-fix route each bug to the RIGHT repo (client custom code vs native platform) and file to the RIGHT tracker. Use when standing the plugin up on a new machine or for a new customer.
Initialize / onboard this agentic-QA plugin onto a deployment. Installs deps, then asks the operator only what genuinely shapes the config — the environment NAME, the bug tracker (Jira / Azure Boards), the code host (GitHub / Azure Repos), and an auth preference per axis (PAT recommended, else browser/CLI login). Everything else — whether it is a native-platform or a CLIENT project, the client org, the contribution mode, the fork account — is DERIVED from the token + the filled env + a live module/repo scan. Writes project-profile.json + .env.<env> + .env.local + .mcp.json and verifies access. The whole point is to make /qa-fix route each bug to the RIGHT repo (client custom code vs native platform) and file to the RIGHT tracker. Use when standing the plugin up on a new machine or for a new customer.
[QA Methodology] Gather ALL fresh CI prerelease artifacts for a change (modules + platform + vc-frontend) and deploy them together to the test env (vc-deploy-dev@<TEST_ENV branch>) in ONE manifest update: resolve a tracker ticket's linked PRs across all repos (or an explicit --module/--platform/--theme/--pr set) → each PR's latest vc3prerelease build → minimal-diff repin of backend/packages.json (AzureBlob/BlobName + PlatformVersion) and theme/artifact.json → dry-run combined diff (default) or a gated deploy PR (direct same-repo when the account has write, else a fork PR) → --verify polls the env-branch pin + /api/platform/modules per target. Never merges (a human merges to deploy); writes route through gh's keyring token; prints the web-edit URL when it can't push. Unblocks /qa-test PR#N and /qa-verify-fix.
[QA Method] Triangulate each BL invariant against docs + live + source code, auto-apply confirmed changes to business-logic.md, and reconcile test-case coverage. Delegates the live axis to qa-testing-expert; runs the triangulation via ba-system-analyzer.
Bring up a local Virto Commerce stack (backend + storefront + DB + ES) via start-local, pinned to the ACTUAL deployed package manifest (vc-deploy-dev @ vcptcore-demo); optionally augment it with the module/PR versions a JIRA task needs. Use when asked to spin up / run / provision a local VC environment, reproduce a deployed env locally, or stand up an env to test a specific ticket.
[QA Method] Defect management lifecycle: JIRA Bug Workflow, triage, classification, report validation, verification protocol, defect metrics.
| 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.