Personal Training OS: Requirements & Traceability
Personal Training OS: Test Cases

Personal Training OS: Test Cases

UID:
VERSION:
CLASSIFICATION:
PREFIX:
Type
Level
UID
PREFIX
REFS
Title
Statement
METHOD
AUTOMATED
SECTION
1
Verification test cases
TEST
1.1
TC-NOTE-SCOPE
TC-NOTE-SCOPE
Suite scope note (2026-07-08; increments verified 2026-07-10 in run-2), not a test case

Scope of this suite. TC-01 through TC-20 verify the v1.0 baseline (recorded baseline run 20/20 test cases Pass on 2026-07-05, plus 7/7 UAT Accept). TC-21 through TC-27 verify the post-release increments (2a-2c Garmin activities, Garmin daily wellness metrics, and Withings weight; 3 hockey auto-schedule; 4 MyFitnessPal nutrition at per-meal grain), added and executed in run-2 on 2026-07-10 (17/17 automated Pass). That run found and fixed defect D-08 (three sync scripts wrote rows without a Person relation) and hardened the baseline cases against live-data mutation. The increments are therefore formally verified, closing the operational-evidence-only gap noted at the v1.0 baseline. This element is a documentation note, not an executable test; it carries no Parent relation and asserts no result. See pm/project-state.md for the authoritative as-built state.
Analysis
No
TEST
1.2
TC-01
TC-01
Hockey not-attended does not count

A hockey session with Attendance = Did Not Attend has Counts Toward Training (auto) = false.
Test
Yes
TEST
1.3
TC-02
TC-02
Hockey attended counts

A hockey session with Attendance = Attended has Counts Toward Training (auto) = true.
Test
Yes
TEST
1.4
TC-03
TC-03
Completed run counts

A non-hockey session with Status = Completed has Counts Toward Training (auto) = true.
Test
Yes
TEST
1.5
TC-04
TC-04
Planned session does not count

A non-hockey session with Status = Planned has Counts = false; setting Status = Completed flips it to true.
Test
No
TEST
1.6
TC-05
TC-05
Shoe mileage rollup equals 16

an example running shoe Total Miles = 16 (sum of Distance from the two linked runs, 11 + 5).
Test
Yes
TEST
1.7
TC-06
TC-06
Rollup updates on new run

Linking a new run to the shoe increases Total Miles; unlinking returns it to the prior value.
Test
No
TEST
1.8
TC-07
TC-07
Secondary User is first-class

Secondary User exists in People and is selectable as Person on sessions/goals/metrics.
Test
Yes
TEST
1.9
TC-08
TC-08
Person filter isolates data

Filtering by Person = Primary User vs Secondary User returns only that person's rows.
Test
No
TEST
1.10
TC-09
TC-09
Manual source default

A hand-created session has Source = Manual.
Inspection
No
TEST
1.11
TC-10
TC-10
Equipment availability correct

Kettlebells, Net, Barbell, Medicine ball = Not available; Stickhandling ball = Pending; the rest Available.
Test
Yes
TEST
1.12
TC-11
TC-11
Templates use available gear only

The seeded Workout Templates reference only Available equipment.
Inspection
No
TEST
1.13
TC-12
TC-12
Race seeds correct

Example Half Marathon = Half Marathon / Goal 2:00:00; Example 5K = 5K.
Test
Yes
TEST
1.14
TC-13
TC-13
Historical runs correct

11-mile long run = 11 mi / Long; 5-mile hill repeats = 5 mi / Hills.
Test
Yes
TEST
1.15
TC-14
TC-14
Session relationships wired

The 11-mile run relates to Person, Running Shoe, Running Route, and Training Block.
Inspection
No
TEST
1.16
TC-15
TC-15
Goal linked to Race

The Sub-2:00 goal has a Race relation to the Example Half Marathon.
Test
Yes
TEST
1.17
TC-16
TC-16
Source-of-truth game link

A hockey session can relate to a Team A/Team B game without altering the source game DB.
Demonstration
No
TEST
1.18
TC-17
TC-17
Page placement

The Personal Training OS page is a child of Personal Dashboard, linked below Inbox.
Inspection
No
TEST
1.19
TC-18
TC-18
Mobile capture

A session/check-in can be logged with low effort in the Notion mobile app.
Demonstration
No
TEST
1.20
TC-19
TC-19
Backup and recovery

The OS data can be exported from Notion and is restorable.
Demonstration
No
TEST
1.21
TC-20
TC-20
Training materials present

At least one running, one strength, and one hockey Workout Template exist, plus Hockey Drills.
Test
Yes
TEST
1.22
TC-21
TC-21
Garmin daily wellness metrics provenance (Increment 2b)

Each Metrics/Check-ins row sourced from Garmin carries a garmin-metrics-<date> Source ID, an Imported At timestamp, and at least one wellness value.
Test
Yes
TEST
1.23
TC-22
TC-22
Withings weight provenance (Increment 2c)

Each Metrics/Check-ins row sourced from Withings carries a withings-<grpid> Source ID, a Weight value, and an Imported At timestamp.
Test
Yes
TEST
1.24
TC-23
TC-23
Garmin activities into Training Sessions (Increment 2a)

Each Training Session row sourced from Garmin carries a Garmin Activity ID and an Imported At timestamp.
Test
Yes
TEST
1.25
TC-24
TC-24
Hockey games auto-scheduled (Increment 3)

Each Training Session row sourced from the Hockey DB links a source game (Gabagools or Bacon).
Test
Yes
TEST
1.26
TC-25
TC-25
MyFitnessPal nutrition at per-meal grain (Increment 4)

Each Nutrition Log row sourced from MyFitnessPal carries an mfp-<date>-<meal> Source ID, a Meal, a Calories value, and an Imported At timestamp.
Test
Yes
TEST
1.27
TC-26
TC-26
Idempotent upsert, unique Source IDs

No two synced rows within a database share a Source ID, confirming idempotent upserts across the Metrics, Nutrition, and Training Sessions databases.
Test
Yes
TEST
1.28
TC-27
TC-27
Synced rows relate to a Person

Every synced row (Garmin, Withings, MyFitnessPal, Hockey DB) across Metrics, Nutrition, and Training Sessions relates to a Person. This case found defect D-08; the fix and a 54-row backfill landed in run-2.
Test
Yes