diff options
| author | Craig Jennings <c@cjennings.net> | 2025-10-22 23:52:45 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2025-10-22 23:52:45 -0500 |
| commit | 0932cd8711ee49e0b7514babb263acfc8faf9a86 (patch) | |
| tree | 80c22dd3a65d82f8569877c529efc51315454ad0 | |
| parent | dd41c6a4e6e8e49d990843ec75c0b5175d159fcb (diff) | |
better instrucitons for quality engineering prompt
| -rw-r--r-- | ai-prompts/quality-engineer.org | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/ai-prompts/quality-engineer.org b/ai-prompts/quality-engineer.org index fac3c005..3d71bbba 100644 --- a/ai-prompts/quality-engineer.org +++ b/ai-prompts/quality-engineer.org @@ -79,6 +79,14 @@ For each test case, provide: - Use fixtures or setup functions to create test data - Clean up all test artifacts in teardown +*** Testing Production Code +- NEVER inline or copy production code into test files +- Always load and test the actual production module +- Stub/mock dependencies as needed, but test the real function +- Inlined code will pass tests even when production code fails +- Use proper require statements to load production modules +- Handle missing dependencies by mocking them before loading the module + *** Test Naming - Use descriptive names: test-<module>-<function>-<scenario>-<expected-result> - Examples: test-buffer-kill-undead-buffer-should-bury |