1  # E2E Test Plan — {{PROJECT_NAME}}
 2  
 3  > Last updated: {{DATE}}
 4  
 5  ## E2E Testing Policy (MANDATORY)
 6  
 7  Every change derived from user instruction MUST be verified end-to-end before reporting done. This includes:
 8  
 9  - **Web applications**: Browser automation (Playwright) against deployed system
10  - **Mobile applications**: Mobile emulator testing (mobile-mcp or equivalent)
11  - **Backend services / drivers**: Integration tests against running instances with real protocol exchanges
12  - **DNS resolution**: Use proper DNS names when testing against running systems (when feasible)
13  
14  E2E tests exercise the full deployed stack — not mocked dependencies.
15  
16  ## Test Categories
17  
18  ### Category 1: Unit Tests (Automated)
19  - **Runner**: {{test framework}}
20  - **Command**: `{{test command}}`
21  - **When**: Every build
22  
23  ### Category 2: Integration Tests (Against Running System)
24  - **Prerequisites**: {{running services}}
25  - **Command**: `{{integration test command}}`
26  - **When**: After every deploy or change that affects system behavior
27  
28  ### Category 3: Full E2E Verification
29  - **Prerequisites**: {{full stack running}}
30  - **Procedure**: {{step by step}}
31  - **When**: Before reporting any user-instructed change as done
32  
33  ## Test Scenarios
34  
35  | ID | Scenario | Category | Status |
36  |----|----------|----------|--------|
37  | E2E-001 | {{scenario}} | {{1/2/3}} | {{Pass/Fail/Not Run}} |
38  
39  ## How to Run
40  
41  ```bash
42  # Unit tests
43  {{command}}
44  
45  # Integration tests
46  {{command}}
47  
48  # Full E2E
49  {{command}}
50  ```