Personal Training OS — Test Cases
A hockey session with Attendance = Did Not Attend has Counts Toward Training (auto) = false.
A hockey session with Attendance = Attended has Counts Toward Training (auto) = true.
A non-hockey session with Status = Completed has Counts Toward Training (auto) = true.
A non-hockey session with Status = Planned has Counts = false; setting Status = Completed flips it to true.
an example running shoe Total Miles = 16 (sum of Distance from the two linked runs, 11 + 5).
Linking a new run to the shoe increases Total Miles; unlinking returns it to the prior value.
Secondary User exists in People and is selectable as Person on sessions/goals/metrics.
Filtering by Person = Primary User vs Secondary User returns only that person's rows.
A hand-created session has Source = Manual.
Kettlebells, Net, Barbell, Medicine ball = Not available; Stickhandling ball = Pending; the rest Available.
The seeded Workout Templates reference only Available equipment.
Example Half Marathon = Half Marathon / Goal 2:00:00; Example 5K = 5K.
11-mile long run = 11 mi / Long; 5-mile hill repeats = 5 mi / Hills.
The 11-mile run relates to Person, Running Shoe, Running Route, and Training Block.
The Sub-2:00 goal has a Race relation to the Example Half Marathon.
A hockey session can relate to a Team A/Team B game without altering the source game DB.
The Personal Training OS page is a child of Personal Dashboard, linked below Inbox.
A session/check-in can be logged with low effort in the Notion mobile app.
The OS data can be exported from Notion and is restorable.
At least one running, one strength, and one hockey Workout Template exist, plus Hockey Drills.