aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2025-10-22 23:52:45 -0500
committerCraig Jennings <c@cjennings.net>2025-10-22 23:52:45 -0500
commitcc15ec0f8babe8c19b64c0077c9c059cbe5c09f8 (patch)
tree9601786a4a4f36fd3d2bdc3528d5bd61faf264fa
parent77a4a93dceeee6f309e42967959dbd52ad6e5ce7 (diff)
downloaddotemacs-cc15ec0f8babe8c19b64c0077c9c059cbe5c09f8.tar.gz
dotemacs-cc15ec0f8babe8c19b64c0077c9c059cbe5c09f8.zip
better instrucitons for quality engineering prompt
-rw-r--r--ai-prompts/quality-engineer.org8
1 files changed, 8 insertions, 0 deletions
diff --git a/ai-prompts/quality-engineer.org b/ai-prompts/quality-engineer.org
index fac3c0054..3d71bbba5 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