QA Templates

# Test Plan: [Project/Feature Name]

## Document Control
| Field | Value |
|-------|-------|
| Version | 1.0 |
| Author | [Name] |
| Date | [Date] |
| Status | Draft / In Review / Approved |

---

## 1. Introduction

### 1.1 Purpose
[Describe the purpose of this test plan]

### 1.2 Scope
[What will and will not be tested]

### 1.3 References
| Document | Version | Location |
|----------|---------|----------|
| Requirements Spec | 1.0 | [Link] |
| Design Doc | 1.0 | [Link] |

---

## 2. Test Strategy

### 2.1 Test Levels

| Level | Description | Responsibility |
|-------|-------------|----------------|
| Unit Testing | Individual functions/methods | Developers |
| Integration Testing | Component interactions | Developers/QA |
| System Testing | End-to-end functionality | QA |
| UAT | User acceptance | Product/Users |

### 2.2 Test Types

| Type | In Scope | Tools |
|------|----------|-------|
| Functional | Yes | [Tools] |
| Performance | Yes | [Tools] |
| Security | Yes | [Tools] |
| Accessibility | Yes | [Tools] |
| Regression | Yes | [Tools] |

### 2.3 Test Approach
[Describe the overall approach - risk-based, requirements-based, etc.]

---

## 3. Test Environment

### 3.1 Environment Configuration

| Component | Test Environment | Production |
|-----------|------------------|------------|
| Server OS | [Version] | [Version] |
| Database | [Version] | [Version] |
| Browser | [Versions] | [Versions] |

### 3.2 Test Data
[Describe test data requirements and how it will be managed]

### 3.3 Test Tools

| Purpose | Tool | Version |
|---------|------|---------|
| Test Management | [Tool] | [Version] |
| Automation | [Tool] | [Version] |
| Performance | [Tool] | [Version] |

---

## 4. Test Schedule

| Phase | Start Date | End Date | Status |
|-------|------------|----------|--------|
| Test Planning | [Date] | [Date] | Complete |
| Test Case Development | [Date] | [Date] | In Progress |
| Test Execution | [Date] | [Date] | Not Started |
| UAT | [Date] | [Date] | Not Started |

---

## 5. Test Deliverables

| Deliverable | Due Date | Owner |
|-------------|----------|-------|
| Test Plan | [Date] | [Name] |
| Test Cases | [Date] | [Name] |
| Test Data | [Date] | [Name] |
| Test Summary Report | [Date] | [Name] |

---

## 6. Entry and Exit Criteria

### 6.1 Entry Criteria
- [ ] Requirements document approved
- [ ] Test environment available
- [ ] Test data prepared
- [ ] Code deployed to test environment

### 6.2 Exit Criteria
- [ ] All planned test cases executed
- [ ] No critical or high severity defects open
- [ ] Test coverage meets [X]% threshold
- [ ] All acceptance criteria verified

---

## 7. Risk Assessment

| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|
| Environment unavailable | Medium | High | Have backup env |
| Insufficient test data | Low | Medium | Prepare early |
| Resource constraints | Medium | High | Cross-train team |

---

## 8. Roles and Responsibilities

| Role | Name | Responsibilities |
|------|------|------------------|
| Test Lead | [Name] | Plan, coordinate, report |
| QA Engineer | [Name] | Execute tests, report bugs |
| Automation Engineer | [Name] | Develop/maintain automation |

---

## 9. Approval

| Role | Name | Signature | Date |
|------|------|-----------|------|
| QA Lead | | | |
| Project Manager | | | |
| Product Owner | | | |

# Test Case: TC-[ID]

## Test Case Information
| Field | Value |
|-------|-------|
| Test Case ID | TC-[ID] |
| Title | [Descriptive title] |
| Priority | High / Medium / Low |
| Type | Functional / Performance / Security |
| Automation Status | Manual / Automated / Candidate |

## Traceability
| Field | Reference |
|-------|-----------|
| Requirement | REQ-[ID] |
| User Story | US-[ID] |
| Design Spec | [Reference] |

---

## Preconditions
[What must be true before this test can execute]

1. User is logged in as [role]
2. Test data [X] exists in system
3. Feature flag [Y] is enabled

---

## Test Steps

| Step | Action | Expected Result |
|------|--------|-----------------|
| 1 | Navigate to [URL/Page] | [Page] is displayed |
| 2 | Enter [value] in [field] | Value is accepted |
| 3 | Click [button] | [Expected behavior] |
| 4 | Verify [element] | [Expected state] |

---

## Test Data
| Data Element | Value | Notes |
|--------------|-------|-------|
| Username | testuser@example.com | Valid user |
| Password | [secure] | Valid password |
| Input value | [value] | [description] |

---

## Postconditions
[Expected state after test completion]

- Database record created with [values]
- Email notification sent
- Audit log entry created

---

## Execution History

| Date | Tester | Environment | Result | Defect |
|------|--------|-------------|--------|--------|
| [Date] | [Name] | [Env] | Pass/Fail | [Bug ID] |

---

## Notes
[Additional context or variations]

# Bug Report: BUG-[ID]

## Bug Information
| Field | Value |
|-------|-------|
| Bug ID | BUG-[ID] |
| Title | [Clear, concise title] |
| Severity | Critical / High / Medium / Low |
| Priority | P1 / P2 / P3 / P4 |
| Status | New / In Progress / Fixed / Verified |
| Reporter | [Name] |
| Assignee | [Name] |
| Date Reported | [Date] |

---

## Environment
| Field | Value |
|-------|-------|
| Environment | Dev / Test / Staging / Prod |
| Browser/Client | [Browser/Version] |
| OS | [OS/Version] |
| Build/Version | [Version] |

---

## Description

### Summary
[One sentence describing the bug]

### Steps to Reproduce
1. [Step 1]
2. [Step 2]
3. [Step 3]
4. [Step 4 - where bug occurs]

### Expected Result
[What should happen]

### Actual Result
[What actually happens]

### Frequency
[Always / Sometimes / Rarely] - [X out of Y attempts]

---

## Impact
[Business impact of this bug]

- Affects [X] users
- Blocks [functionality]
- Causes [data issue/security concern]

---

## Attachments
- Screenshot: [filename]
- Video: [filename]
- Logs: [filename]

---

## Additional Context
[Any other relevant information]

- Related to [feature/component]
- Possibly caused by [recent change]
- Workaround: [if any]

---

## Resolution

### Root Cause
[After investigation - what caused the bug]

### Fix Description
[What was changed to fix it]

### Fix Version
[Version where fix is included]

### Verified By
[Name] on [Date] in [Environment]

# Test Summary Report

## Report Information
| Field | Value |
|-------|-------|
| Project | [Project Name] |
| Release | [Version] |
| Test Period | [Start Date] - [End Date] |
| Report Date | [Date] |
| Author | [Name] |

---

## Executive Summary

### Overall Status: [PASS / CONDITIONAL PASS / FAIL]

[2-3 sentence summary of testing outcomes and release readiness]

---

## Test Scope

### Features Tested
- [Feature 1]
- [Feature 2]
- [Feature 3]

### Features Not Tested
- [Feature X] - Reason: [reason]

### Out of Scope
- [Item] - Reason: [reason]

---

## Test Execution Summary

### By Test Type
| Test Type | Total | Passed | Failed | Blocked | Not Run |
|-----------|-------|--------|--------|---------|---------|
| Functional | [X] | [X] | [X] | [X] | [X] |
| Regression | [X] | [X] | [X] | [X] | [X] |
| Integration | [X] | [X] | [X] | [X] | [X] |
| Performance | [X] | [X] | [X] | [X] | [X] |
| **Total** | **[X]** | **[X]** | **[X]** | **[X]** | **[X]** |

### Pass Rate
- Overall: [X]%
- Critical Path: [X]%

---

## Defect Summary

### By Severity
| Severity | Found | Fixed | Open | Deferred |
|----------|-------|-------|------|----------|
| Critical | [X] | [X] | [X] | [X] |
| High | [X] | [X] | [X] | [X] |
| Medium | [X] | [X] | [X] | [X] |
| Low | [X] | [X] | [X] | [X] |

### Open Defects
| ID | Title | Severity | Status | Notes |
|----|-------|----------|--------|-------|
| BUG-XXX | [Title] | High | In Progress | [Notes] |

---

## Test Coverage

### Requirements Coverage
| Category | Total Reqs | Tested | Coverage |
|----------|------------|--------|----------|
| Functional | [X] | [X] | [X]% |
| Non-Functional | [X] | [X] | [X]% |

### Code Coverage
| Metric | Target | Actual |
|--------|--------|--------|
| Line Coverage | [X]% | [X]% |
| Branch Coverage | [X]% | [X]% |

---

## Risk Assessment

### Residual Risks
| Risk | Severity | Mitigation |
|------|----------|------------|
| [Open bug X] | Medium | [Workaround available] |
| [Untested area] | Low | [Low usage feature] |

---

## Exit Criteria Assessment

| Criterion | Target | Actual | Met? |
|-----------|--------|--------|------|
| Test execution | 100% | [X]% | ✅/❌ |
| Pass rate | 95% | [X]% | ✅/❌ |
| Critical bugs | 0 | [X] | ✅/❌ |
| High bugs | 0 | [X] | ✅/❌ |

---

## Recommendations

### Release Recommendation
[Ready for Release / Conditional Release / Not Ready]

### Conditions (if applicable)
- [Condition 1]
- [Condition 2]

### Post-Release Monitoring
- Monitor [metric/feature]
- Watch for [potential issue]

---

## Approval

| Role | Name | Decision | Date |
|------|------|----------|------|
| QA Lead | [Name] | Approve/Reject | [Date] |
| Dev Lead | [Name] | Approve/Reject | [Date] |
| Product Owner | [Name] | Approve/Reject | [Date] |