write-testslisted

# Write Tests Write the appropriate unit, integration, component, and end-to-end tests: **$ARGUMENTS** ## Process Follow these steps in order: 1. **Understand the project's test conventions** - Identify the language, runtime, package boundary, and every test runner relevant to the requested tests - Inspect dependencies, imports, runner configuration, package scripts, setup files, CI commands, and representative existing tests - Load every matching language and runner reference that exists: - `references/junit.md` - `references/typescript.md` - `references/vitest.md` - `references/jest.md` - `references/node-test.md` - `references/bun-test.md` - `references/playwright.md` - In monorepos and migrations, determine runner ownership per package and test file; do not assume one runner governs the repository - Repository conventions and installed-version behavior override greenfield defaults 2. **Analyse the code under test** - Identify the public interface and critical business logic - Map dependencies and external interactions - Note error conditions, edge cases, and validation rules - Follow repository coverage thresholds and use coverage to identify consequential gaps rather than gaming a universal percentage 3. **Plan the test strategy** - Decide which levels are needed: unit, integration, end-to-end - List what to mock or stub, and why - Prioritise business-critical paths first 4. **Write unit