Skip to checklist
Tennis RosterLaunch companion
Release log
Development checksMade for your phone

A quick check.
Then back to court.

Your pocket checklist for the latest development changes. Keep it open while you try the app in another tab.

Open development app (opens in a new tab)

Before you start

Use a disposable dev roster with made-up players. Export a full backup of any original roster in Settings before changing it. Run these checks only on dev.roster.tennis, never on production.

This is a public checklist. It contains no private launch notes, accounts or source files.

Your quick checks

01 — 07

Open a check in a new tab, try it on dev, then come back to tick it.

  1. Confirm dev & sign in

    Open Account, check the address is dev.roster.tennis, then sign in with your development account.

    What should happen

    Your account and intended development workspace are shown. Stop if you are on production.

  2. Try the phone navigation

    Move between Home, Players, Schedule and Results. Open More, visit Settings, then reopen and close More.

    What should happen

    Labels stay readable, taps work after loading, and More opens and closes without trapping the page.

  3. Create a disposable season

    Back up any existing roster first. In More, choose New roster. Complete the season details and add a few made-up players.

    What should happen

    Details and players survive a reload. Switching rosters still shows the original season unchanged.

  4. Preview fixtures, then cancel

    On the disposable roster, preview a fixture import from a file you already have. Compare team, season, dates, venues and full street addresses with its source.

    What should happen

    No-play, final and spare weeks keep their labels. Cancel adds no fixtures; reload confirms that. Source files are not supplied by this companion.

  5. Change just one lineup

    Add two ordinary test rounds if needed. Change the players or pairs in one round, then inspect the other round and reload.

    What should happen

    Only the chosen round changes. The other lineup, snack assignments and existing results stay as they were.

  6. Save a partial result

    Enter part of a score and reload. Check its incomplete state, then finish the result and reload again.

    What should happen

    The partial score survives without being treated as complete. The finished result survives too, with other rounds unchanged.

  7. Check a dev cloud round trip

    Back up local changes in every open app tab. For your disposable dev cloud roster, use Account → Save active roster to cloud, then Settings → Browse Workspace Schedules to load that same test roster.

    What should happen

    Success appears only after a confirmed save; loading restores the test roster. Keep original backups. If cloud access is unavailable, leave this unticked.

Keep the bigger checks for later

Two-tab conflicts, offline recovery, the full import corpus and production readiness are not certified by this phone check. Keep those in the full launch review.

See what changed