Production Lines
QA Certification: {Product Name}
QA Certification: {Product Name}
Order: {order-id} Client: {client-name} Product type: {product-type} QA Engineer: Quinn Date started: {start-date} Date completed: {completion-date}
1. Product Information
| Field | Value |
|---|---|
| Product name | {product-name} |
| Order ID | {order-id} |
| Client | {client-name} |
| Product type | {product-type} |
| Working language | {language} |
| Skills count | {count} |
| Build completed by | Pablo (Production Line Architect) |
| Build sign-off date | {date} |
2. Test Environment
| Field | Value |
|---|---|
| Repository path | {repo-path} |
| Claude Code version | {version} |
| Test data location | {test-data-path} |
| Test date range | {start-date} to {end-date} |
| Models used during testing | {list models used} |
3. Functional Test Results
Tests derived from work order capabilities. Each capability must have at least one functional test.
| Test ID | Skill Tested | Test Description | Expected Result | Actual Result | Status | Notes |
|---|---|---|---|---|---|---|
| FT-001 | /{command} |
{What is being tested} | {Expected behavior} | {Actual behavior} | PASS/FAIL | {Notes} |
| FT-002 | /{command} |
{What is being tested} | {Expected behavior} | {Actual behavior} | PASS/FAIL | {Notes} |
| FT-003 | /{command} |
{What is being tested} | {Expected behavior} | {Actual behavior} | PASS/FAIL | {Notes} |
| FT-{nnn} | /{command} |
{What is being tested} | {Expected behavior} | {Actual behavior} | PASS/FAIL | {Notes} |
Functional tests passed: __ / __ total Functional pass rate: ___%
4. Edge Case Test Results
Standard edge cases applied to all products, plus product-specific edge cases from the work order.
| Test ID | Skill Tested | Test Description | Expected Result | Actual Result | Status | Notes |
|---|---|---|---|---|---|---|
| EC-001 | {all/specific} | Empty input provided | Reports missing input, no garbage output | {Actual} | PASS/FAIL | {Notes} |
| EC-002 | {all/specific} | Ambiguous request | Asks clarifying questions or escalates | {Actual} | PASS/FAIL | {Notes} |
| EC-003 | {all/specific} | Conflicting requirements in input | Identifies conflict, flags for human | {Actual} | PASS/FAIL | {Notes} |
| EC-004 | {all/specific} | Large input exceeding typical size | Handles without truncation or degradation | {Actual} | PASS/FAIL | {Notes} |
| EC-005 | {all/specific} | Wrong skill invoked for the task | Redirects to correct skill or reports mismatch | {Actual} | PASS/FAIL | {Notes} |
| EC-{nnn} | /{command} |
{Product-specific edge case} | {Expected} | {Actual} | PASS/FAIL | {Notes} |
Edge case tests passed: __ / __ total Edge case pass rate: ___%
5. Documentation Test Results
| Test ID | Document Tested | Test Description | Method | Status | Notes |
|---|---|---|---|---|---|
| DT-001 | User Guide | Workflows described match actual behavior | Follow each workflow, verify steps | PASS/FAIL | {Notes} |
| DT-002 | Skill Reference Card | Skill descriptions match actual I/O | Run each skill, compare against reference | PASS/FAIL | {Notes} |
| DT-003 | CLAUDE.md | Skills table matches .claude/commands/ files |
Compare table rows to actual files | PASS/FAIL | {Notes} |
| DT-004 | Configuration Guide | Config instructions are accurate and complete | Follow each config step, verify result | PASS/FAIL | {Notes} |
| DT-005 | Quick Start | Quick start steps work end-to-end | Follow as a new user would | PASS/FAIL | {Notes} |
| DT-{nnn} | {Document} | {Additional doc test} | {Method} | PASS/FAIL | {Notes} |
Documentation tests passed: __ / __ total Documentation pass rate: ___%
6. Scoring
| Category | Tests Passed | Tests Total | Pass Rate | Threshold | Status |
|---|---|---|---|---|---|
| Functional | __ | __ | ___% | 100% required | PASS/FAIL |
| Edge Cases | __ | __ | ___% | >= 80% required | PASS/FAIL |
| Documentation | __ | __ | ___% | 100% required | PASS/FAIL |
Scoring Rules
- PASS: Functional 100% AND Edge Cases >= 80% AND Documentation 100%
- CONDITIONAL: Functional 100% AND Edge Cases >= 60% with remediation plan
- FAIL: Any functional failure OR Edge Cases < 60%
7. Verdict
| Field | Value |
|---|---|
| Overall verdict | PASS / CONDITIONAL / FAIL |
| Functional | PASS / FAIL |
| Edge Cases | PASS / FAIL |
| Documentation | PASS / FAIL |
8. Remediation Plan (if CONDITIONAL or FAIL)
{If verdict is PASS, write "N/A -- no remediation required." and skip the table.}
| Issue ID | Test ID | Description | Severity | Remediation Action | Owner | Target Date | Status |
|---|---|---|---|---|---|---|---|
| REM-001 | {test-id} | {What failed} | {Critical/High/Medium/Low} | {What needs to be done} | {Who fixes it} | {When} | {Open/In Progress/Resolved} |
| REM-002 | {test-id} | {What failed} | {Severity} | {Action} | {Owner} | {Date} | {Status} |
Remediation Conditions
- All Critical and High severity items must be resolved before deployment
- Medium and Low items may ship with documented workarounds
- Re-test required after remediation: Yes / No
9. Sign-Off
| Field | Value |
|---|---|
| QA Engineer | Quinn |
| Verdict | PASS / CONDITIONAL / FAIL |
| Date | {date} |
| Signature | ___________________________ |
Conditional Approval Notes (if applicable)
{If CONDITIONAL, document: what conditions must be met before deployment, deadline for remediation, who is responsible.}