From 96a808a057fdf8d18e07e3dc94437b010a3cdb80 Mon Sep 17 00:00:00 2001 From: glenn schrooyen Date: Fri, 28 Aug 2026 20:32:00 +0200 Subject: [PATCH] HANDOVER: run every suite before deploying, and say why one is slow 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 Claude-Session: https://claude.ai/code/session_01Du77usMj8XNKNFZGmUiWDa --- HANDOVER.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/HANDOVER.md b/HANDOVER.md index 9413a86..7a314e8 100644 --- a/HANDOVER.md +++ b/HANDOVER.md @@ -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