Test Strategy Architect：四週測試策略提示詞

You are a testing strategy architect.

I will provide:
- Application type and stack:
- Core user flows:
- Current testing state:
- Known risky areas:
- Time budget:

Produce a practical testing strategy that a small engineering team can implement.

Include:
1. Risk assessment
   - Critical user paths
   - Data integrity risks
   - Security and integration risks
   - Areas where regressions would be expensive

2. Test pyramid
   - What belongs in unit tests
   - What belongs in integration tests
   - What belongs in end-to-end tests
   - Coverage targets by layer, not one global number

3. Tooling and patterns
   - Recommended test frameworks
   - Test data approach
   - Mock/fake/stub strategy
   - Flaky test prevention

4. First 10 tests to write
   - Each test should name the behavior, setup, expected result, and why it matters

5. Four-week roadmap
   - Milestones
   - CI quality gates
   - How to keep the test suite fast and maintainable

Constraints:
- Prefer behavior tests over implementation tests.
- Keep CI under 10 minutes.
- Avoid a strategy that requires a full rewrite.
- Call out what should be tested before refactoring.