Integration Test Cases
Each test case is one action taken in a single system, paired with the expectations that must then hold in both systems — because an action in one system must produce a result that looks natively created in the other (native-equivalence).
How to read each table
Three columns. Column 1 is always one action — where it's performed and what it is. Columns 2 and 3 are checklists — each item is a separate thing to verify. Cases are grouped by where the action originates.
🖥️ Origin
Actions an operator performs in the Setpoint admin (PMS). Verify the result on both sides.
| Action & Location | 🖥️ Expected in Setpoint Admin | 📱 Expected in TPS Mobile App |
|---|---|---|
Setpoint Admin → Create a booking (assign it to a customer whose email matches a TPS account) |
|
|
Setpoint Admin → Schedule a coaching lesson (book a player with a coach; player email matches a TPS account) |
|
|
Setpoint Admin → Schedule a coaching lesson on a court that was previously booked then freed (REGRESSION: an earlier booking on that exact court + time was cancelled, OR a lesson hold on it expired. The slot must read as free everywhere and the lesson must actually save. (Bug: availability showed "1 court free" but Create Lesson failed with "Court has a conflicting booking" because the create-check counted cancelled/expired bookings — fixed 2026-05-25.)) |
|
|
Setpoint Admin → Cancel a booking (a booking that exists for a matching TPS user) |
|
|
Setpoint Admin → Cancel a coaching lesson (cancel a lesson that exists for a matching TPS user) |
|
|
📱 Origin
Actions a player performs in the TPS mobile app (consumer). Verify the result on both sides.
| Action & Location | 🖥️ Expected in Setpoint Admin | 📱 Expected in TPS Mobile App |
|---|---|---|
TPS Mobile App → Book a court (signed in as a TPS user) |
|
|
TPS Mobile App → Book a coaching lesson (signed in as a TPS user; book a coach. RE-TEST 2026-05-28 on an OpenRally club (Sandbox Pad Thai Padel): the coaching court is now derived from OpenRally live availability instead of TPS's stale local table (BUG-097), and the Setpoint hold now covers the full payment window (BUG-098). Only the court-correctness + payment-window items below need re-verifying; the rest of the flow is unchanged.) Tested by Gian · 2026-05-28 · booking #60839 (PASSED) |
|
|
TPS Mobile App → Cancel a booking (signed in as a TPS user; cancel an existing booking) Tested by Alba · 2026-05-21 · C-06 (PASSED) |
|
|
TPS Mobile App → Cancel a coaching lesson (signed in as a TPS user; cancel an existing coaching lesson) |
|
|