메뉴
[Testing] Generate test case writing checklists for any domain, feature, or regression area. Uses 63 built-in domain checklists (33 storefront + 29 backend/admin + 1 GraphQL) + custom creation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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-checklist |
| description | [Testing] Generate test case writing checklists for any domain, feature, or regression area. Uses 63 built-in domain checklists (33 storefront + 29 backend/admin + 1 GraphQL) + custom creation. |
| argument-hint | domain name | feature | VCST-XXXX | new <domain> | admin <module> |
| disable-model-invocation | true |
Generate or retrieve domain-specific checklists that ensure complete test case coverage. Each checklist item maps to at least one test case.
/qa-checklist auth # Retrieve Auth storefront checklist
/qa-checklist "product configurations" # Retrieve Product Configs & Variations checklist
/qa-checklist graphql # Retrieve GraphQL xAPI checklist (separate file)
/qa-checklist admin catalog # Retrieve Catalog Admin checklist (backend file)
/qa-checklist admin pricing # Retrieve Pricing Admin checklist
/qa-checklist VCST-1234 # Generate checklist for JIRA ticket scope
/qa-checklist new "push messages" # Create new checklist for unlisted domain
/qa-checklist all # List all 63 domain checklists with item counts
Checklist items are written to be testable; they assume readers will resolve test data and verify schemas via the canonical sources, not hardcode values:
| File | Use when |
|---|---|
../qa-postman/test-data-fixtures.md + test-data/aliases.json | Any checklist item that mentions a specific entity (product, org, address, coupon, card, store) — resolve via @td(ALIAS.field) instead of inventing values |
../../../agents/knowledge/api/graphql-schema.md | Any GraphQL query/mutation/field name in a checklist item — verify it exists in the live schema before deriving a test case |
../../../agents/knowledge/api/graphql-test-cases-runner.md | Authoring runner-native GraphQL test cases derived from graphql-checklist.md items (CSV format, [GQL-OP]/[GQL-VARS]/[GQL-EXEC]/[GQL-CAPTURE] grammar) |
../../../agents/knowledge/oracles/business-logic.md | Cross-link checklist items to BL-* invariants in the Business_Rule column of derived test cases |
domain-checklists.md| # | Domain | Items | Related Suites |
|---|---|---|---|
| 1 | Auth | 8 | 01, 02, 08 |
| 2 | Catalog | 28 | 01, 03, 16 |
| 3 | Categories | 6 | 03, 16 |
| 4 | SEO | 8 | 31 |
| 5 | Add to Cart | 11 | 01, 04a |
| 6 | Search | 12 | 03, 26 |
| 7 | Ship-to Selector | 9 | 04a, 04b |
| 8 | Cart/Checkout | 19 | 04a, 04b, 06 |
| 9 | Payment | 12 | 06 |
| 10 | Orders | 11 | 01, 04c, 20 |
| 11 | Company Info | 6 | 02, 21 |
| 12 | Company Members | 12 | 02, 21 |
| 13 | Multi-Org | 13 | 02, 21 |
| 14 | Product Configurations & Variations | 58 | 36 |
| 15 | PDP (Product Detail Page) | 11 | 01, 03 |
| 16 | Google Analytics | 11 | 07 |
| 17 | Anonymous Flow | 8 | 04a, 04b |
| 18 | Cart Merge | 11 | 04a, 30 |
| 19 | BOPIS (Pickup) | 12 | 05, 30 |
| 20 | B2B Quotes & RFQ | 14 | 04c, 20 |
| 21 | B2B Lists & Quick Order | 13 | 13 |
| 22 | Localization & i18n | 7 | 10 |
| 23 | Notifications | 12 | 24 |
| 24 | White Labeling | 13 | 32, 35 |
| 25 | Account Management | 13 | 01, 02, 13 |
| 26 | Storefront Push Messages | 12 | 33 |
| 27 | Coupons & Promotions | 12 | 41, 23, 42 |
| 28 | Security | 10 | 08 |
| 29 | Accessibility | 10 | 09 |
| 30 | Performance | 8 | 11 |
| 31 | Browser Compatibility | 7 | 12 |
| 32 | B2C Features | 10 | 13 |
| 33 | Subscriptions & Recurring Orders | 10 | 14 |
| BF | Bug Fix Verification | 10 | per bug |
backend-admin-checklists.mdAligned with Bundle v14.0.8 (Platform 3.1007.2, 53 modules).
| # | Domain | Module(s) | Items | Related Suites |
|---|---|---|---|---|
| A1 | Catalog Admin | VirtoCommerce.Catalog | 12 | 16 |
| A2 | Pricing Admin | VirtoCommerce.Pricing | 10 | 19 |
| A3 | Inventory Admin | VirtoCommerce.Inventory | 9 | 22 |
| A4 | Orders Admin | VirtoCommerce.Orders | 10 | 20 |
| A5 | Customer Admin | VirtoCommerce.Customer | 10 | 21 |
| A6 | Marketing Admin | VirtoCommerce.Marketing | 10 | 23 |
| A7 | Store Admin | VirtoCommerce.Store | 9 | 18 |
| A8 | Notifications Admin | VirtoCommerce.Notifications | 9 | 24 |
| A9 | Content & Pages (CMS) | Content, Pages, PageBuilderModule | 10 | 25 |
| A10 | Search & Indexing | Search, ElasticSearch8 | 9 | 26 |
| A11 | Assets Admin | Assets, AzureBlobAssets | 8 | 27 |
| A12 | Core Settings | VirtoCommerce.Core | 9 | 28 |
| A13 | Platform Security & Users | Platform Core | 10 | 17 |
| A14 | CSV Import/Export | CatalogCsvImportModule, Export | 10 | 29 |
| A15 | Shipping Admin | VirtoCommerce.Shipping | 8 | 30 |
| A16 | SEO & Sitemaps | Seo, Sitemaps | 9 | 31 |
| A17 | Image Tools | VirtoCommerce.ImageTools | 8 | 34 |
| A18 | Tax | Tax, AvalaraTax | 7 | — |
| A19 | Subscriptions | VirtoCommerce.Subscription | 8 | — |
| A20 | WebHooks | VirtoCommerce.WebHooks | 7 | — |
| A21 | Customer Reviews | VirtoCommerce.CustomerReviews | 7 | — |
| A22 | Dynamic Associations | DynamicAssociationsModule | 6 | — |
| A23 | Bulk Actions | BulkActionsModule | 6 | — |
| A24 | GDPR | VirtoCommerce.GDPR | 5 | — |
| A25 | Catalog Personalization | CatalogPersonalization | 5 | — |
| A26 | Catalog Publishing | CatalogPublishing | 5 | 40 |
| A27 | Payment Admin | Payment, AuthorizeNetPayment | 6 | — |
| API1 | Platform REST API | Platform | 10 | 14 |
| API2 | GraphQL xAPI | Xapi, XCart, XCatalog, XOrder | 12 | 15 |
graphql-checklist.md| # | Domain | Items | Related Suites |
|---|---|---|---|
| GQL | GraphQL Queries & Mutations | 34 | 15 |
Sections: xCatalog (4), xCart Lifecycle (9), xCart Configurable (2), xCart Wishlists & Saved (2), xOrder (2), xProfile (6), xQuote (2), xCMS & xFrontend (2), Cross-Cutting (3), New Query/Mutation Verification (8).
Total: 738 checklist items across 63 domains + 1 cross-domain checklist (storefront: 411 + admin: 244 + GraphQL detail: 83).
admin <module> prefix routes to backend-admin-checklists.md ("admin catalog" → A1, "admin pricing" → A2, "admin orders" → A4)graphql-checklist.md for detailed query/mutation checklist, or API2 for high-level xAPI coveragedomain-checklists.md, backend-admin-checklists.md, or graphql-checklist.mdgraphql-checklist.md — include the "New Query/Mutation Verification" section for any new or modified queries/mutationsnew keyword)checklist-creation-guide.md for methodologydomain-checklists.md (UI domains) or as a separate file (API/backend domains) — ask user for confirmationall keyword)domain-checklists.md and graphql-checklist.md### [Domain Name] — Test Case Writing Checklist
> X items | Related suites: XX, XX | Priority: P0/P1
- [ ] Item description (specific, actionable, uses real UI labels)
- [ ] Item description
- ...
**Cross-layer checks:**
- [ ] Storefront UI reflects expected state
- [ ] No console errors or failed network requests
- [ ] Admin confirms data persisted correctly
**Related checklists:** [Domain A], [Domain B]
e2e-scenario-catalog.md) for related scenarios| Skill | Relationship |
|---|---|
/qa-plan | Checklists feed into test plan creation — ensures no domain is missed |
/qa-test-design | Checklist items can be expanded using EP, BVA, decision tables |
/qa-risk | High-risk domains get more granular checklist items |
/qa-sbtm | Checklists serve as starting point for exploratory session charters |
/qa-api | GraphQL xAPI checklist aligns with xAPI test execution and case generation |
knowledge/domain/sitemap.md | Sitemap provides URLs and product types for UI exploration |