Menü
[QA Method] Evidence capture & report formatting: screenshot rules, 3-tier verbosity, output paths.
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-evidence |
| description | [QA Method] Evidence capture & report formatting: screenshot rules, 3-tier verbosity, output paths. |
| argument-hint | [compact|detailed|signoff] |
Apply the project's evidence capture policy and output path conventions. Use before any test execution session to ensure consistent artifact collection.
/qa-evidence # Full policy review (capture rules + output paths)
/qa-evidence compact # Compact reporting tier rules
/qa-evidence detailed # Detailed reporting tier rules
/qa-evidence signoff # Sign-off reporting tier rules
tests/, bugs → reports/bugs/, regression → reports/regression/, raw browser output → test-results/)| When | What | Naming |
|---|---|---|
| Test FAILS | Failure state screenshot | {TC-ID}-FAIL-{description}.png |
| Bug found | Bug evidence (annotated) | BUG-{name}-evidence.png |
| Visual regression | Before/after comparison | {component}-{state}-{viewport}.png |
| Critical flow final state | Confirmation/success page | {flow}-final-state.png |
| Error state | Console panel, network 500, error toast | {TC-ID}-error-{type}.png |
| Tier | Use When | Content |
|---|---|---|
| Compact | Regression suite pass, smoke run | Pass/fail table + bug list only |
| Detailed | Sprint testing, JIRA ticket testing | Full test case results + evidence |
| Sign-Off | Pre-release, stakeholder review | Detailed + summary + risk assessment |
| Artifact | Directory |
|---|---|
| Test docs (plans, cases, reports) | reports/tickets/SprintXX-XX/VCST-XXXX/ |
| Screenshots (test evidence) | reports/tickets/SprintXX-XX/VCST-XXXX/screenshots/ |
| Bug reports | reports/bugs/ |
| Bug evidence | reports/bugs/screenshots/, reports/bugs/api-traces/ |
| Regression reports | reports/regression/ |
| Raw browser artifacts (gitignored) | test-results/{browser}/ |
test-results/ (gitignored)tests/ or reports/ (tracked)