admin/goodwe-addon
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

HANDOVER: run every suite before deploying, and say why one is slow

Browse Source 
The pre-deploy command listed three of the five suites; test_validate and
test_p1 were never added when they arrived. Adds those and test_loop, with a
note that test_loop's ~35 s is the cost of proving a wall-clock property about a
loop that sleeps 1 s a tick rather than a sign something is wrong.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Du77usMj8XNKNFZGmUiWDa
This commit is contained in:
glenn schrooyen
2026-08-28 20:32:00 +02:00
co-authored by Claude Opus 5
parent 88cd97cc7a
commit 96a808a057
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
HANDOVER.md
+6 -1
View File
@@ -52,9 +52,14 @@ Run the checks before deploying. No framework needed:
```bash
cd goodwe_controller
python3 test_control.py && python3 test_maintenance.py && python3 test_arbiter.py
python3 test_control.py && python3 test_maintenance.py && python3 test_arbiter.py \
&& python3 test_validate.py && python3 test_p1.py && python3 test_loop.py
```
⚠️ `test_loop.py` takes about **35 seconds** and that is not a bug. It drives the real
control loop, which sleeps 1 s a tick, to prove a wall-clock property about it
(SAFETY-12); mocking the clock there would leave the assertion testing the mock.
---
## 3. Known broken / unfinished