iOS Manual QA Tester — React Native health-tracking app (TestFlight)
We're preparing a React Native / Expo iOS app for external TestFlight and need
an experienced manual QA tester to run a structured test plan and report bugs.
The app is a private daily health-tracking tool (protein/weight/medication
logging, calendar, PDF export, a small community feed). We will provide a
TestFlight build and dedicated TEST accounts with fabricated data only — you
will never see or need real personal or health information.
SCOPE
- 200+ test cases across: sign-up/sign-in (email, Google, Apple), onboarding,
daily logging, calendar, PDF/CSV/XLSX export, in-app alerts and local
reminders, a community feed (posts/replies/block/report), profile & account
deletion, accessibility (VoiceOver, Dynamic Type, iPad layout), and
two-account data-isolation checks.
- Many cases are short and straightforward — e.g. check a label, confirm a
screen opens, verify a button state, or spot-check layout/copy. A smaller
set is heavier (multi-step auth, account deletion, reminders, two-account
checks). Steps and expected results are written out; you are not inventing
the plan.
- You'll work in our Jira Cloud project with the AIO Tests plugin: each case
ID, steps, and expected results live there (already prioritized P0 first).
On hire you'll get access to run executions and update results in place.
- Each case: follow the steps, mark Pass / Fail / Blocked in AIO, add
findings/comments on the case or run, and link or file a bug for any
mismatch.
- Testing is on a PHYSICAL iPhone via TestFlight (a native build — not Expo
Go). A second device (older/smaller iPhone, or iPad) is a plus.
PHASE 0
- Run the 47-case release-smoke subset first (~2-4 hours), provided as a
separate short checklist / AIO cycle.
- Deliverable: smoke cycle updated in AIO (Pass / Fail / Blocked) + any
bugs filed in the format below.
- We confirm the full engagement after reviewing this.
PHASE 1 — main engagement
- Run the remaining ~161 cases (208 minus the Phase 0 smoke subset),
P0 → P1 → P2 in the order given in AIO.
- Deliverable: every remaining case executed in AIO with Result / notes
updated, plus a Jira bug (or equivalent) for each failure, using the
format below.
BUG REPORT FORMAT (per issue)
- Title (one line)
- Test case ID (e.g. TC-LOG-MED-014)
- Steps to reproduce
- Expected result
- Actual result
- Severity (Critical / High / Medium / Low)
- Screenshot or screen recording
- Device + iOS version
REQUIREMENTS
- Own a physical iPhone capable of running current iOS and installing
TestFlight builds (simulators are not sufficient — several flows use Face
ID, native Apple/Google sign-in sheets, and real push/lock-screen
notifications).
- Solid manual QA / mobile app testing background — please share examples.
- Comfortable following a detailed written test plan exactly, not just
free-form exploring.
- Comfortable working in Jira / a test-management tool (AIO Tests or
similar) to mark executions and attach findings — we will give a short
walkthrough on day one if needed.
- Clear written English for bug reports (you're the only person who will
have seen the failure).
- Prior QA on a health, fintech, or other privacy-sensitive app is a plus.
- Must be willing to sign a short NDA before receiving build/test-account
access (standard for an app handling health-adjacent data, even with
fabricated test data).
WHAT WE PROVIDE
- TestFlight invite
- Test account credentials (fabricated data — no real user information)
- Jira Cloud + AIO Tests access (cases, cycles, and bug filing)
- The written test plan as backup reference, plus the 47-case smoke set
- A point of contact for questions during testing
SCREENING QUESTIONS
1. Have you tested a native iOS app via TestFlight before (not just web)?
Briefly describe the app and your role.
2. Do you have a physical iPhone available for this (not a simulator)?
Which model / iOS version?
3. Have you signed an NDA for QA work before? Any concerns doing so here?
4. Have you used Jira (or AIO / Zephyr / Xray / similar) to execute test
cases and log bugs? Briefly what you used.
5. Paste an example bug report you've written (redact anything
confidential).