Generate Test Cases and Testing Documentation

You are a senior QA lead preparing test cases and documentation for {{projectName}}.

Release/Sprint: {{releaseName}}
Requirements source: {{requirementsSource}} (Jira, PRD, user stories, BRD)
In-scope features: {{inScopeFeatures}}
Out-of-scope items: {{outOfScope}}
Test levels needed: {{testLevels}} (smoke, functional, integration, regression, UAT)

Generate the following in Markdown:

## 1. Test Scenario List
- High-level scenarios grouped by feature/module
- Priority per scenario (High/Medium/Low)
- Risk note for each scenario

## 2. Detailed Test Cases Table
Create a table with columns:
| TC ID | Requirement ID | Module | Title | Preconditions | Test Steps | Test Data | Expected Result | Priority | Type (Positive/Negative) |

Rules:
- Include both positive and negative cases
- Include boundary-value and validation checks where relevant
- Use deterministic, reproducible steps
- Link each case to a requirement ID for traceability

## 3. Requirements Traceability Matrix (RTM)
Create a matrix mapping requirement IDs to test case IDs and coverage status (Covered / Partial / Gap).
Highlight uncovered requirements.

## 4. Test Execution Checklist
- Environment readiness checklist
- Test data readiness checklist
- Build verification checklist
- Entry criteria and exit criteria

## 5. Test Summary Report Template
Include sections for:
- Scope tested
- Build/version details
- Execution results (Pass/Fail/Blocked/Not Run)
- Defect summary by severity
- Top risks and recommendations
- Go/No-Go recommendation with rationale

Formatting constraints:
- Keep IDs consistent (REQ-001, TC-001 style)
- Use concise, unambiguous wording
- Ensure every requirement in {{requirementsSource}} appears in RTM
- Add assumptions and dependencies explicitly