# Vajraya Labs — sample QA delivery structure

**This is a blank deliverable template, not a completed customer project or evidence of observed defects.**

**Engagement:** [agreed scope]  
**Target application and version:** [identifier]  
**Environment:** [OS/browser/API version/test dataset]  
**Execution date:** [date]  
**Tester:** [name]  
**Access and limitations:** [credentials, exclusions, inaccessible paths]

## Summary
- Tests planned / executed / passed / failed / blocked: [counts]
- High-risk findings: [number and summary]
- Release impact: [recommendation; not a certification]

## Finding [ID]
- **Severity/priority:** [agreed rubric]
- **Affected path:** [URL/API/feature]
- **Preconditions:** [setup and permissions]
- **Steps to reproduce:** [numbered exact steps]
- **Expected behavior:** [expected]
- **Observed behavior:** [actual]
- **Evidence:** [redacted logs/screenshots/request IDs]
- **Reproducibility:** [repeat count, environment]
- **Suggested next check:** [bounded proposal]
- **Retest status:** [NOT_RUN / PASS / FAIL / BLOCKED, timestamp]

## Residual gaps
- Untested conditions: [list]
- Missing evidence: [list]
- Proposed follow-up: [specific action]

## Delivery
- Defect log, reproduction instructions, test notes, and bounded regression results provided on [date].