System test plan
How a release system-test run works — environments, devices, test data, entry/exit criteria, and how results are recorded.
Tracking app — system tests
Manual system-test protocol for @enode/tracking. Each case covers requirement IDs from the tracking/shared catalogs and records pass/fail.
Portal — system tests
Manual system-test protocol for @enode/portal. Each case covers requirement IDs from the portal/shared catalogs and records pass/fail.
Auth test plan
Canonical full-path case matrix for authentication (login, register, roles, deletion, redirects) and how each case is covered — unit, live API, browser smoke, or server-side.
Auth backend handoff
What the backend team needs to mirror the auth case matrix server-side — wire contract, curl templates, dev conventions the client suite depends on, and the open contract questions the live runs surfaced.
Planner — Manual Test Protocol
Click-through QA script for the portal Planner (calendar, scheduling, workout builder). Each case has steps and an expected result so a tester can record pass/fail.
test-runs
1 item
User drawer — Manual Test Protocol
Click-through QA script for the portal's user drawer (roster visibility, tabs, Summary, Goals, Schedule, Activity, caching and invalidation). Each case has steps and an expected result so a tester can record pass/fail.