Chuyển Product Acceptance Criteria thành test matrix và xUnit integration/API contract tests trước khi code, bao phủ happy path, validation, authorization, edge cases, tiếng Việt có dấu, security payloads và business rules từ BRD.
Use this skill before implementation for any backend/API behavior change, and after implementation to verify the result.
Keep this skill low-coupled and high-cohesion: QC owns traceability and test coverage, not project-specific architecture. Resolve test directory, namespace, framework and commands from the current project context before generating files.
QC can use multiple input sources:
Figma MCP must not override BRD/AC. Use it to derive UI/UX test coverage and API contract expectations only after Product has confirmed the business rule.
true.Should().BeTrue().python3 .agents/skills/qc_agent/scripts/qc_test_generator.py --entity "<EntityName>" --route "<api-route>" --test-dir "<test-dir>" --namespace "<test-namespace>" --actions "Create,GetById,Validation,Unauthorized,Vietnamese,Security"Example with explicit project adapter values:
python3 .agents/skills/qc_agent/scripts/qc_test_generator.py --entity "VisitBooking" --route "visit-bookings" --test-dir "apps/api/tests/Acme.Api.Tests" --namespace "Acme.Api.Tests"Import from traditional tester Excel/CSV test cases:
python3 .agents/skills/qc_agent/scripts/qc_test_generator.py --entity "MealRating" --testcase-file "testcases/MealRating.xlsx" --sheet "API Test Cases" --test-dir "apps/api/tests/Acme.Api.Tests" --namespace "Acme.Api.Tests" --dedupe skipAttach Figma MCP/design traceability when tests come from a design frame:
python3 .agents/skills/qc_agent/scripts/qc_test_generator.py --entity "VisitBooking" --route "visit-bookings" --test-dir "apps/api/tests/Acme.Api.Tests" --namespace "Acme.Api.Tests" --platform web --design-source "Figma MCP: Website / Visit Booking" --figma-node "123:456" --design-note "Form có loading, disabled submit, validation lỗi số điện thoại và success state"Combine Excel import with Figma/design source when a tester file maps to a screen:
python3 .agents/skills/qc_agent/scripts/qc_test_generator.py --entity "VisitBooking" --testcase-file "testcases/VisitBooking.xlsx" --sheet "UI API Contract" --test-dir "apps/api/tests/Acme.Api.Tests" --namespace "Acme.Api.Tests" --platform web --design-source "Figma MCP: Visit Booking frame" --figma-node "123:456" --dedupe skipRecommended columns:
TestCaseIdScenarioMethodRouteInputExpectedStatusCodeExpectedResultActorProtectedBusinessRuleDuplicate handling:
--dedupe skip skips duplicate imported rows by test signature.--dedupe error fails fast when a duplicate is detected.--overwrite is required to replace an existing generated file.Create_WithValidRequest_ShouldReturnCreatedCreate_WithMissingRequiredField_ShouldReturnBadRequestGetById_WithUnknownId_ShouldReturnNotFoundRequest_WithoutToken_ShouldReturnUnauthorized when endpoint is protected.# [Feature] - QC Test Plan
## Traceability
| AC | Test ID | Automation | Notes |
| --- | --- | --- | --- |
## API Contract
- Method:
- Route:
- Request:
- Response:
- Status codes:
- Design source/Figma node:
## Test Cases
| Test ID | Scenario | Input | Expected | Type |
| --- | --- | --- | --- | --- |
## Generated/Updated Files
- Project-specific test path from context.
## Verification
- Command:
- Result:solana8800/vclaw-ui
e5978b4
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.