summaryrefslogtreecommitdiff
path: root/docs/TESTING.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/TESTING.md')
-rw-r--r--docs/TESTING.md14
1 files changed, 14 insertions, 0 deletions
diff --git a/docs/TESTING.md b/docs/TESTING.md
index 4443a90..6063740 100644
--- a/docs/TESTING.md
+++ b/docs/TESTING.md
@@ -26,6 +26,20 @@ Test devices: the Forerunner 70 by default; with `ALL=1` (`TEST_DEVICES`): Forer
## Results
+### Review of 0.9.0, 2026-10-26 (unreleased)
+
+An independent review of 0.9.0's changes (b8addc8, 096b5a4, 404b505, 140a666) and a watchdog test of the PIN unlock found and fixed:
+
+- After a correct PIN, promoting pending entries and applying waiting "Require PIN" changes ran in one event; 16 waiting changes tripped the watchdog on the Forerunner 70. It is now a job (`ChangeQueue.LockJob`), and `make watchdog` has nine vault cases (19 items in total; PERFORMANCE.md).
+- The list title decrypted every waiting change at each start; a 1 KB replacement was enough to trip at two passes. Changes are now counted from their stored action codes.
+- A replacement was only checked after the PIN; it is now checked when it arrives, and its material is stored apart (`qm.<n>`).
+- "Confirm all" applied changes that arrived after the menu was read; Confirm all and Reject all now act only on what the menu showed.
+- On touch screens START could submit a legacy PIN early; "Change PIN" with a legacy PIN asked twice; a lock applied when a PIN is set didn't refresh the glance; the results of applied locks were lost.
+
+Rejected: a tap opening the focused row instead of the tapped one (not reproducible in the simulator; watch for it in round 2), and the 250 ms ticker on a locked code card (cost negligible next to the screen).
+
+Unit tests: 176 per device, including `test/settings/ChangeQueueTest.mc`. Two Forerunner 70 goldens changed (`list_locked`, `list_reset`: the title says "Results ready (menu)" after the lock applied at the PIN).
+
### Real-watch fixes, 2026-10-25 (version 0.9.0)
The first real-watch round on the Forerunner 70 (docs/YOUR_STEPS.md parts 3 and 4, 2026-10-21) reported: no touch scrolling outside the menus, a hard-to-use PIN keypad, "Wrong PIN" once before a correct PIN opened the code, more digits typed than dots shown, the QR progress starting at 90 %, and Manage entry's Require PIN not applying. All are fixed (CHANGELOG 0.9.0). Unit tests: 168 per device.