Tester Guide

Updated: 2026-09-21 10:44 ET

TLDR: Sign in → person icon → Settings → tap the version number 5 times (turns on Diagnostic Mode). Then ☰ menu (top-left) → Page Readiness. The Ready to Test tab lists everything you can try right now — tap a row to open it. Then follow the matching Tester Walkthrough: steps, screenshots, what you should see, and what a failure looks like.

Written for hands-on testers — no coding background needed. For the automated test suites or joining the TestFlight / Google Play beta, see the Testing guide instead.

1 · The Page Readiness screen

The app opens on Home in the new design (or on the log-in screen if you are signed out).

Turn on Diagnostic Mode first — the Page Readiness row is hidden without it: sign in, tap the person icon (top-right) → Settings → tap the version number at the bottom 5 times. A message confirms it's on. On a beta build it stays on for a day; on an engineering build it resets when the app is closed. Diagnostic Mode has its own walkthrough.

Then, from any screen, open the ☰ menu (top-left) and tap Page Readiness.

Page Readiness screen, Ready to Test tab, Area dropdown on Show all

Where you land — Area on Show all.

Page Readiness screen filtered to the KCM area

The same screen with KCM chosen.

Old design: the previous app is still installed. With Diagnostic Mode on, the same ☰ menu has Exit to Native Home for side-by-side comparison; the Blazor Dev tile (first tile on that grid) brings you back.

2 · Tester Walkthroughs — the index

One row per walkthrough. Start from names the Page Readiness row (or Settings path) each one opens with; walkthroughs that need Diagnostic Mode say so.

WalkthroughWhat it coversStart from
Sign-in and the signed-out app
Login & Logout Member and non-member sign-in, the Auth Status utility, log out, and what a logged-out visitor can browse (Check 8). Login — Member · Login — Non-Member · Auth Status / Log Out · Profile (log out)
Signed-Out Home The signed-out Home landing: instant paint with no loading skeleton, and the "New content" refresh pill — shown on demand via Diagnostic Mode, and applying it swaps in the new content. Log out, open Home. Checks 2–3 need Diagnostic Mode.
Home and member content
Promo Banner The live banner slot on ALPA Home and the MEC page: image vs. composite layout, external-browser vs. in-app-modal tap-through, dismissing. Page Banner test — render / tap / dismiss
Favorites Saving with the heart, the list, swipe-to-remove, the empty state, and the "content no longer available" fallback. Favorites — save / list / remove / empty state · Home Preview — heart-toggle test surface (Checks 2–3)
Documents Category rows and article lists, the in-app viewer for PDF and HTML documents, and prefetch. Documents section: Internal Comms · Document viewer — Canadian Limits PDF · MEC Documents
Search On-device search over already-cached content: grouped results with highlighted matches, the category filter, and what tapping each content type opens. Search — local on-device results (requires login)
Member Resources The resource list and its four destinations: Orange Card, In Case of Accident, International Directory (sticky search), Membership Card with barcode. Member Resources section: Member Resources — resource list
Advocacy The ALPA-PAC contribution card and its web hand-offs, the meeting-report hand-off, and Calls to Action. Advocacy — PAC contributions / calls to action (requires login)
MEC Hotels The airport-grouped hotel directory and its live search (airport code, airport name, hotel name), the hotel detail page, favoriting, and the sign-out reset. Screenshots still to be added. Home → View My MEC → COMMITTEES → HOTEL → HOTEL LIST TEST (requires login)
Jumpseat and KCM
Flight Finder Jumpseat search with typeahead and guard rails, flight cards with live leg statuses, sort/filter, airline policies, saved and recent lists. Jumpseat / Flight Finder section: Flight Finder Search → Results → Flight Detail · Airline Policies · Saved / Recent
Known Crewmember (KCM) Airline eligibility table, crew-role filter, airports list with the NOTICE advisory, airport check-in details. Works logged out. KCM section: KCM Home · KCM Airlines · KCM Airports
Notifications
Notifications The Comms inbox with its audience filter, Flight Finder alerts grouped by flight with update history, and what a tapped push notification opens (Checks 7–8). Notifications section: Notifications — Comms + Flight Finder · Push / Deep-link Test Scenarios
FTDT (Flight Time / Duty Time)
FTDT Cumulative limits dashboard, duty periods and their forms (flight segment, rest, note), the rest-rules engine, and the test-scenario seeder. FTDT section: FTDT Dashboard · Add Duty Period · Test Scenarios (Beta)
Settings and diagnostics
Diagnostic Mode The hidden Settings gesture (tap the version number 5 times) that reveals the DIAGNOSTICS group. Prerequisite for the next three rows and for Signed-Out Home Checks 2–3. Profile (person icon) → Settings → version number
Refresh Auth Token The Diagnostics modal that re-signs you in with stored credentials and re-fetches all content, showing live per-endpoint status. Use it after a portal-side change to your account. Settings → DIAGNOSTICS → Refresh Auth Token (needs Diagnostic Mode, a stored password)
App Logs The on-device log viewer. Works signed in or out. Settings → DIAGNOSTICS → App Logs (needs Diagnostic Mode)
Device, accessibility, and the browser
Accessibility & Zoom Pinch-zoom inside a document without zooming the app chrome, zoom resetting between documents, rotation / landscape rules on phone and iPad. Any document from the Documents walkthrough
Text Scaling The app at the phone's largest system text size: tab bar goes icons-only, hero cards drop their image. Device only. Phone Settings → text size, then Home
In-App Browser The signed-in web view every ALPA website link opens in, with its floating back / forward / refresh / close cluster. Any website link — e.g. the Advocacy PAC card

Empty State Scenarios (all areas) has no walkthrough — the page explains each row in place. It is a design-review utility, useful when you need to see a screen with nothing on it.

Maintainers: one row per walkthroughs/<feature>/ directory. Adding, renaming, or removing a walkthrough updates this table in the same change; renaming a Page Readiness row updates its Start from cell.

3 · Adding a new Tester Walkthrough

For whoever builds the next walkthrough (engineer or QA lead) — skip if you're here to test.
  1. Start from walkthroughs/TEMPLATE.md; write the page as walkthroughs/<feature>/index.html, screenshots in a sibling screen-assets/ folder.
  2. Capture every screenshot live against the running app — never mock one up.
  3. Each check follows Steps → Screenshot → Expected result → What a failure looks like, in tester-facing language (a card, a heart icon, a menu row — not component names).
  4. Close with What this checks, overall and What's not covered yet.
  5. Add its row to the index above and spot-check the finished page against a live simulator.