From 52c3165d1ddd54f1a5fd71fcaa711a4a8754676a Mon Sep 17 00:00:00 2001 From: Dominik Jain Date: Sat, 8 Aug 2026 13:05:00 +0200 Subject: [PATCH] Add more concrete instructions on test strategy in system prompt --- .serena/project.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.serena/project.yml b/.serena/project.yml index 0e57ea7b..44f5f231 100644 --- a/.serena/project.yml +++ b/.serena/project.yml @@ -85,7 +85,11 @@ initial_prompt: | For simple data storage, you use dataclasses instead of dictionaries or tuples. Testing: - You test externally observable behavior and guarantees, never implementation structure. + The key principle is to test *only* externally observable behavior and guarantees, never implementation structure. + * Litmus test: a behaviour-preserving refactoring must not break any test. A test that could break is wrong and must not be written. + * When functionality is removed, you delete its tests. You never add tests asserting the *absence* of something; + absence of an implementation detail is not a behaviour, and such tests only freeze the current implementation and burden maintenance. + * Fewer, behaviour-anchored tests are preferred; a missing test is better than an implementation-coupled one. Docstrings & Comments: * You consistently use reStructuredText.