ALPR PRIVACY / BUILD & USE
Test what the device actually does.
Use observable results, and keep a record of the hardware and firmware revision.
| Check | Expected observation / next action |
|---|---|
| Power and boot | Stable startup without repeated resets. Record board revision and firmware version. |
| Startup self-tests | For v0.4.1, Serial Monitor should report database-updater and trigger-counter self-test results. Investigate any failure before relying on updates. |
| Storage | Original compatible database opens. Keep an external backup of the card. |
| GPS outdoors | A usable fix and accuracy appear; compare against a known location. |
| Maintenance | A brief button press opens Privacy Wi-Fi and the local page; timeout occurs after browser inactivity. |
| Output | Verify an entry adds one activation and remaining inside adds none, using a controlled bench test. Verify exit/reset behavior separately. |
| Trigger retention | Normal restart retains the count when NVS is preserved. |
| Database download | Known compatible release downloads, verifies and selects the intended inactive SD slot. |
| Normal restart after update | The selected verified database is re-opened. |
| Interrupted download | Using an isolated bench test, incomplete staging data is not selected; known-good data remains usable. |
| Recovery | Test a deliberately invalid candidate only in an isolated test build/feed. Confirm fallback before unattended operation. |
Keep the acceptance record useful
Record the date, exact board and GPS model, source revision, supply, SD card, database release and observed result for each check. Leave a test marked pending until it has run on the real device.