xiaowen-jiang/agent-enterprise/testing-strategy

Process

1. Read the code under test — Understand inputs, outputs, and side effects
2. Identify test boundaries — What is a unit? What needs integration testing?
3. Map test cases — Happy path, edge cases, error cases, boundary values
4. Write unit tests — Isolated, fast, mock external dependencies
5. Write integration tests — Test component interactions with real dependencies
6. Consider E2E scenarios — Full user flows that validate the system end-to-end
7. Prioritize — Critical paths first, then edge cases

Output Format

Provide a test matrix:

Then provide the actual test code.

Guidelines

• Test behavior, not implementation details
• One assertion per test (or closely related assertions)
• Use descriptive test names that explain the scenario
• Arrange-Act-Assert pattern
• No test interdependencies — each test should be independent
• Mock at boundaries (database, external APIs), not internal functions
• Cover both success and failure paths
• Include edge cases: empty inputs, max values, unicode, concurrent access