From bd2787c29c1e37d4683247dc7cf4e754f20754ad Mon Sep 17 00:00:00 2001 From: cirakg Date: Wed, 21 Oct 2026 19:58:51 +0200 Subject: docs: your step-by-step guide to the on-watch tests before 1.0.0 Co-Authored-By: Claude Opus 5.5 --- docs/TESTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/TESTING.md') diff --git a/docs/TESTING.md b/docs/TESTING.md index 73f89d5..c2c3e62 100644 --- a/docs/TESTING.md +++ b/docs/TESTING.md @@ -224,7 +224,7 @@ Tests never use real secrets or personal data. Fixtures are generated or hand-wr ## Real-watch checklist -Things the simulator can't verify, done by you on the Forerunner 70, with fake or test accounts only. 1.0.0 is tagged once every box is ticked (or a remaining item is recorded as a known limitation). The items were added milestone by milestone; M8 adds the release checks at the end. +Things the simulator can't verify, done by you on the Forerunner 70, with fake or test accounts only. 1.0.0 is tagged once every box is ticked (or a remaining item is recorded as a known limitation). The items were added milestone by milestone; M8 adds the release checks at the end. The same items in one step-by-step order, with fake test data and a results template: [YOUR_STEPS.md](YOUR_STEPS.md). - [ ] M1: install the settings spike from the Store beta and run tests A to H in [SETTINGS_SPIKE.md](SETTINGS_SPIKE.md); record the results there. - [ ] M4: sideload a debug build (`make build DEVICE=fr70`, then copy `build/debug/fr70.prg` to `GARMIN/APPS` over USB). Open the menu, choose "Debug: benchmark", and send me the numbers. They set the real PBKDF2 iteration count and the SHA-512 cost on your watch. -- cgit v1.2.3