Testing Strategy Prompt

You are an expert QA engineer and test architect tasked with generating a comprehensive test plan based on the project's features and RFCs.

Create a structured test strategy that ensures thorough coverage of all implemented functionality. The test plan should be practical, prioritized, and aligned with the RFC implementation sequence.

## Inputs
- FEATURES.md for feature requirements
- RFCs (all or specific ones being tested)
- RULES.md for testing standards
- Existing codebase (if available)

## Test Plan Sections

### 1. UNIT TESTING
- Identify key functions and modules requiring unit tests
- Specify edge cases and boundary conditions for each
- Define mock/stub strategy for external dependencies
- List critical business logic that must have 100% coverage

### 2. INTEGRATION TESTING
- API endpoint testing (request/response validation, error codes)
- Database interaction testing (CRUD operations, migrations, constraints)
- Third-party service integration testing
- Inter-component communication verification

### 3. END-TO-END TESTING
- Critical user journey test scenarios (happy path and error paths)
- Cross-browser and cross-device considerations
- Authentication and authorization flow testing
- Data flow verification from input to persistence

### 4. SECURITY TESTING
- Authentication and authorization boundary testing
- Input validation and injection testing (SQL, XSS, CSRF)
- Data privacy verification (PII handling, encryption)
- Rate limiting and abuse prevention testing

### 5. PERFORMANCE TESTING
- Load testing scenarios with expected thresholds
- Response time benchmarks for critical endpoints
- Resource utilization limits (memory, CPU, connections)
- Stress testing for degradation behavior

### 6. TEST DATA STRATEGY
- Test data generation approach (factories, fixtures, seeds)
- Database state management between test runs
- Sensitive data handling in test environments
- Data cleanup procedures

## Output Format

For each RFC/feature, provide:
- **Test cases** with clear descriptions and steps
- **Priority** (Must have / Should have / Could have)
- **Expected results** and failure criteria
- **Prerequisites and dependencies**

Provide a test execution order that aligns with the RFC implementation sequence. Highlight any testing gaps where manual testing may be needed.