[GH-ISSUE #19] Validate the packaged MVP on a real laptop and an authorized Traccar receiver #20

New Issue

2026-10-23T18:09:17+02:00

jayanezj commented

2026-10-23 18:09:17 +02:00

Originally created by @jayanezj on GitHub (Oct 23, 2026).
Original GitHub issue: https://github.com/jayanezj/traccar-client-macos/issues/19

Goal

Verify the laptop use case and actual receiver interoperability before accepting the MVP, beyond synthetic tests and a green CI build.

Scope

Test the installed candidate on the M1 reference laptop: explicit start/pause, foreground app changes, closed Settings, lock, sleep/wake, offline queue/reconnect, login and tracking restoration preferences.
Record a repeatable idle/paused/active observation of CPU use, wakeups and energy impact with environment, duration and settings. Investigate sustained busy loops, needless polling and sleep prevention; do not invent a battery-life guarantee or a threshold not agreed with the maintainer.
After explicit authorization, configure the real receiver/identifier privately, send a controlled normal position and inspect its appearance under the intended existing device. Include a small offline/recovery case preserving capture timestamps. Do not alter server infrastructure or device records as a prerequisite.
Keep SOS protocol/error checks on local synthetic fixtures unless a real alarm test is separately authorized. An ordinary receiver test does not authorize an SOS.
Use installation/minimum-OS evidence from PROTO-016 and document stationary capability/fallback and ad hoc permission/Keychain limitations.

Acceptance criteria

The packaged application demonstrates effective pause and predictable sleep/reconnect behaviour on the reference laptop.
Resource observations and any fixes are recorded; no claim rests only on a simulated timer or hosted runner.
The authorized integration confirms the intended device and actual receiver/history behaviour beyond an HTTP 2xx response.
Real coordinates, endpoint and identifier remain outside public artifacts and diagnostic logs.
Unavailable authorization, OS coverage or hardware evidence remains explicitly pending; no external sends occur automatically to complete this checklist.

Validation

Use a short reproducible manual checklist with observed results and sanitized evidence. Fix failures through their owning implementation issues and rerun only affected checks. This validates the agreed laptop MVP, not every Apple Silicon chip or a new server deployment.

Dependencies

Originally created by @jayanezj on GitHub (Oct 23, 2026). Original GitHub issue: https://github.com/jayanezj/traccar-client-macos/issues/19 ## Goal Verify the laptop use case and actual receiver interoperability before accepting the MVP, beyond synthetic tests and a green CI build. ## Scope - Test the installed candidate on the M1 reference laptop: explicit start/pause, foreground app changes, closed Settings, lock, sleep/wake, offline queue/reconnect, login and tracking restoration preferences. - Record a repeatable idle/paused/active observation of CPU use, wakeups and energy impact with environment, duration and settings. Investigate sustained busy loops, needless polling and sleep prevention; do not invent a battery-life guarantee or a threshold not agreed with the maintainer. - After explicit authorization, configure the real receiver/identifier privately, send a controlled normal position and inspect its appearance under the intended existing device. Include a small offline/recovery case preserving capture timestamps. Do not alter server infrastructure or device records as a prerequisite. - Keep SOS protocol/error checks on local synthetic fixtures unless a real alarm test is separately authorized. An ordinary receiver test does not authorize an SOS. - Use installation/minimum-OS evidence from [PROTO-016](https://github.com/jayanezj/traccar-client-macos/issues/16) and document stationary capability/fallback and ad hoc permission/Keychain limitations. ## Acceptance criteria - [ ] The packaged application demonstrates effective pause and predictable sleep/reconnect behaviour on the reference laptop. - [ ] Resource observations and any fixes are recorded; no claim rests only on a simulated timer or hosted runner. - [ ] The authorized integration confirms the intended device and actual receiver/history behaviour beyond an HTTP 2xx response. - [ ] Real coordinates, endpoint and identifier remain outside public artifacts and diagnostic logs. - [ ] Unavailable authorization, OS coverage or hardware evidence remains explicitly pending; no external sends occur automatically to complete this checklist. ## Validation Use a short reproducible manual checklist with observed results and sanitized evidence. Fix failures through their owning implementation issues and rerun only affected checks. This validates the agreed laptop MVP, not every Apple Silicon chip or a new server deployment. ## Dependencies - [PROTO-011](https://github.com/jayanezj/traccar-client-macos/issues/11) - [PROTO-012](https://github.com/jayanezj/traccar-client-macos/issues/12) - [PROTO-016](https://github.com/jayanezj/traccar-client-macos/issues/16)

jayanezj added this to the M5 - Distribution and MVP acceptance milestone 2026-10-23 18:09:17 +02:00

jayanezj added the area:tracking priority:high type:task labels 2026-10-23 18:09:17 +02:00

jayanezj added type:task and removed type:task labels 2026-10-30 18:01:12 +01:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: jayanezj/traccar-client-macos#20