git:20260430.b20ed11 to git:20260719.526b0d1

3 added, 3 removed. Audit A to A.

---

name: test-implement

- description: Test implementation patterns and conventions. Use when implementing unit tests, integration tests, or E2E tests, including RTL+Vitest+MSW component testing and Playwright E2E testing.

+ description: Implements React/TypeScript unit, integration, and browser E2E tests with the repository's configured runner, mocks, setup, and browser harness. Use when creating or completing frontend tests and generated test skeletons.

---

# Test Implementation Patterns

## Reference Selection

| Test Type | Reference | When to Use |

|-----------|-----------|-------------|

- | **Unit / Integration** | [references/frontend.md](references/frontend.md) | Implementing React component tests with RTL + Vitest + MSW |

- | **E2E** | [references/e2e.md](references/e2e.md) | Implementing browser-level E2E tests with Playwright |

+ | **Unit / Integration** | [references/frontend.md](references/frontend.md) | Implementing React component tests with the repository's configured runner and network mocking layer |

+ | **E2E** | [references/e2e.md](references/e2e.md) | Implementing browser-level E2E tests in the existing harness, or Playwright when the approved work introduces a harness |

## Common Principles

### AAA Structure

All tests follow **Arrange-Act-Assert**:

- **Arrange**: Set up preconditions and inputs

- **Act**: Execute the behavior under test

- **Assert**: Verify the expected outcome

### Test Independence

- Each test runs independently without depending on other tests

- No shared mutable state between tests

- Deterministic execution — no random or time dependencies without mocking

### Naming

- Test names describe expected behavior from user perspective

- One test verifies one behavior