iOS TestFlight Checklist

Manual QA for Surfaces/Mobile iOS via TestFlight. Features under test: Features/Mobile Features. Process: Testing/Testing Mechanism.

Prep (A)

1. Update HaloRT in TestFlight → Install → open app.
2. Confirm web admin login works if doing push tests — Testing/Web Admin Checklist.
3. Allow Notifications for HaloRT on the iPhone.

Tenant slug under test: gp2.

B — Login & navigation

1. Type slug gp2 → continue. Community name appears (not a picker list).
2. Login (Google or magic link) → Beranda, HaloRT header, bottom tabs visible.
3. Wrong slug (e.g. gp2xxx) → error message, no crash.
4. Logout → login again → returns to slug screen and can re-enter.

C — Iuran

1. Tab Iuran → pull to refresh. Tagihan list or clear message if unit rumah missing (not 404).
2. If unpaid exists → Bayar; form opens; success or clear failure.
3. Status after pay matches web (Features/Web Features).

D — Kampanye & Pasar

1. Kampanye → pick campaign → Donasi (entire green button, not only text).
2. Pasar → Pasang Iklan (full button hit target). Description min length enforced.
3. Same listing visible on web / admin.

Pengaduan (regression)

1. Layanan → Pengaduan → submit (default kategori Keluhan) with title + body.
2. Appears under “Pengaduan saya” with status.
3. Optional: anonymous + WA number.

F — Push pengumuman (priority)

1. App logged in as warga GP2, notifications ON; app in background (not force-quit).
2. From admin web, publish pengumuman (Testing/Web Admin Checklist E3).
3. Wait 1–2 minutes.

Check: lock screen / Notification Center; tap opens related content; Berita → Pengumuman shows item. If no push but in-app visible, report that explicitly.

G — Cross-check

See cross-check section in Testing/Testing Mechanism.

Known past defects (fixed — retest)

• Primary buttons (Donasi / Pasang Iklan / Logout) only tappable on text — full contentShape fix on iOS.

Related

Surfaces/Mobile Android · Auth · Concepts/Pasar GP2 · Notifications