tiennm99/serena
1
0 Fork 0
mirror of https://github.com/tiennm99/serena.git synced 2026-10-13 20:15:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add more concrete instructions on test strategy in system prompt

Browse Source
This commit is contained in:
Dominik Jain authored and Dominik Jain committed 2026-08-08 13:05:09 +02:00
1 parent c7af2c09ef
commit 52c3165d1d
1 file changed
+5 -1
Download Patch File Download Diff File Expand all files Collapse all files
.serena/project.yml
+5 -1
View File
@@ -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.