QA test: Full QA – 5 Flows iOS App — 2026-08-18

Before you apply

• Access to a device that can open https://testflight.apple.com/join/bJDU7eGv
• iPhone running iOS (physical device required, no Android or simulator)
• TestFlight app installed prior to testing

Task

Install the app via the TestFlight link on your iPhone. No account creation or login is required. Work through each of the 5 flows below one at a time, thoroughly testing all interactive elements, transitions, and edge cases. Report any bugs, crashes, freezes, unexpected behavior, confusing UI, or broken functionality you encounter in each flow. 1. **Narrative Flow** - Open the Narrative flow and complete it end to end. - Test all interactive elements (buttons, inputs, navigation). - Note any crashes, broken transitions, missing content, or confusing UX. 2. **Delivery Flow** - Open the Delivery flow and complete it end to end. - Test all interactive elements and navigation steps. - Report any bugs, errors, or unexpected behavior. 3. **Find the Words Flow** - Open the Find the Words flow and complete it end to end. - Test word selection, submission, and any feedback mechanisms. - Note any incorrect behavior, freezes, or display issues. 4. **Think It Through Flow** - Open the Think It Through flow and complete it end to end. - Test all prompts, inputs, and progression logic. - Report any logical errors, broken steps, or UI issues. 5. **Media Training Flow** - Open the Media Training flow and complete it end to end. - Test all media elements, interactions, and navigation. - Report any playback issues, broken elements, or unexpected behavior. **General guidance:** - Test on a physical iPhone running a current iOS version. - Try tapping quickly, going back and forward, and any other stress interactions to surface edge case bugs. - Your screen recording should capture the full session across all 5 flows with narration explaining what you are doing and what issues you find. - Written findings should list each bug clearly with the flow name, steps to reproduce, and what you expected vs. what happened.

Submission requirements

Video assignments require spoken microphone narration throughout. Captions, written narration, and on-screen text are not substitutes.

1. 1Complete the assigned test stepsFollow every instruction above. If a step is blocked, name the exact step and explain what prevented it.
2. 2Describe test coverageList the steps, pages, controls, devices, and paths you actually tested.
3. 3Report concrete resultsExplain what happened, what worked, and any confusing or poor experience you observed.
4. 4Provide the required video evidenceAttach an MP4, MOV, or WebM screen recording no larger than 75 MB with spoken microphone narration throughout, plus at least one representative screenshot. Captions, written narration, and on-screen text do not replace the required microphone audio.
5. 5Map every attachment to the reportIn the same chat message as each upload, explain what every attached file shows and which tested step or finding it supports.
6. 6Make every issue reproducibleFor each issue, include a short title, severity, expected behavior, actual behavior, and exact reproduction steps.
7. 7Still report useful observations if nothing failedA no-issue result must still say exactly what you tested and include concrete usability observations.