Test Quality Standards for Vibe Bot

When writing or reviewing test cases, follow these standards:

Core Principles

Minimal code: Each test case should be the simplest possible code that demonstrates the pattern. Avoid elaborate setups, complex methods, or unnecessary fields.

Focused: One test case per distinct scenario. Don't combine multiple patterns in a single test.

Brief comments: Use // Compliant or // Compliant: [2-4 words]. Avoid lengthy explanations. If a URL reference gives context, use that instead of block comments.

Integrate into existing methods: Add new test cases to existing test methods when the scenario belongs there, rather than creating separate methods with full setups.

Scope-appropriate: Match test code style to the rule's scope. Tests scope → test-style code (test classes, assertions). Main scope → production-style code. All scope → either is acceptable.

Follow existing conventions: Match the patterns, naming, and structure already established in the test file and similar test files.

No redundancy: If multiple variations test essentially the same thing, keep the clearest version. Each test must add unique coverage.