QA test: iOS TestFlight QA: Rent A Human app 1.1.0 (23) on a real iPhone — 2026-10-17

Before you apply

• Access to a device that can open https://testflight.apple.com/join/VGzXsfve
• Owns and will test on a physical iPhone (not an iPad, simulator, or Android device) on a current iOS version
• Can install apps from Apple's TestFlight app and screen-record with microphone narration in English

Task

Submission requirements

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

Each required test item must be backed by video evidence: a timestamped range in your recording or a short clip.

1. 1Install via TestFlight and verify version 1.1.0 (23)Open the TestFlight link on the iPhone, install TestFlight if needed, accept, install Rent A Human. On camera, show the TestFlight app page with version 1.1.0 (23), then open the app. Note iPhone model and iOS version. Report any install errors verbatim.
2. 2First launch and walkthroughNarrate the first-launch experience: splash, walkthrough/intro screens, skip/continue buttons. Note anything unclear, slow, cut off, or misaligned. Try rotating, swiping back, and backgrounding then reopening the app once.
3. 3Sign up, email verification, sign out, sign inCreate a new account with an email you control and a new password. Pause or obscure the recording for password entry, one-time codes, verification links, and private inbox content. Resume immediately afterward and narrate whether the verification email arrived and its link worked, without exposing the link or credentials. Complete onboarding prompts, sign out from the profile tab, then sign back in. Try one wrong password to see the error message. Optionally try Continue with Apple or Google with your own account.
4. 4Browse jobs, search/filter, open job detailsOn the home tab, scroll the job list, use any search and filter controls, clear them, and pull to refresh. Open at least 3 job detail pages (remote and in-person if available). Check pay, location, requirements, and description display correctly. Do NOT submit applications to real jobs.
5. 5Applications/screening screens and My Work tab (no real applications)Open the apply screen on a job to see what it asks for (screening questions, LinkedIn, mic/language check etc.) and then back out WITHOUT submitting. Open the applications / My Work tab and narrate the empty state and anything shown. Report confusing wording or dead ends.
6. 6Messages tab and job alert notification settingsOpen the Messages tab and narrate the empty state (do not message anyone). Open notification / job alert settings, toggle options, and note the iOS notification permission prompt and what happens if you allow or deny. Report whether settings stick after leaving and returning.
7. 7Wallet and payout screens (look only, no money movement)Open the Wallet tab. Narrate balances, history, and any payout/withdraw setup screens. You may open setup screens to see what they ask for, but do NOT enter bank/card details, deposit, withdraw, or transfer money.
8. 8Profile, edit profile, and settingsOpen your profile, edit it (name, bio, skills, location, profile photo from your library), save, and confirm the changes show after leaving and returning. Check settings, help/legal links, and sign-out. Note photo-library permission prompt wording.
9. 9Permission readiness and attendance/check-in (only on an assigned test job)Note any camera, photo, location, motion, or notification permission prompts you saw and whether their wording is clear. Check any alerts-readiness or permission cards. Only start attendance or a selfie check-in if you were assigned a dedicated test job in writing; otherwise mark this part Not tested and explain.
10. 10Written bug report with repro steps, severity, device and buildSubmit the written report: device model, iOS version, app version/build, numbered bugs with steps/expected/actual/severity/video timestamp, a pass/fail/not-tested line for every checklist item, and your top 3 improvement ideas.
11. 11Complete the assigned test stepsFollow every instruction above. If a step is blocked, name the exact step and explain what prevented it.
12. 12Describe test coverageSay which steps, pages, controls, and paths you actually exercised. Name the device or browser you used only when the task asks for it or when it changes what you found.
13. 13Report concrete resultsExplain what happened, what worked, and any confusing or poor experience you observed.
14. 14Provide the required video evidenceAttach an MP4, MOV, or WebM screen recording no larger than 512 MB, plus at least one representative screenshot.
15. 15Support results with evidenceProvide evidence that supports the completed work and reported findings. Captions are optional; uploads and your written report can be sent in separate chat messages.
16. 16Make every issue reproducibleFor each issue, include a short title, severity, expected behavior, actual behavior, and exact reproduction steps.
17. 17Still report useful observations if nothing failedA no-issue result must still say exactly what you tested and include concrete usability observations.