QA test: Weekly /qa + requester payment funnel QA — 2026-09-10

Before you apply

• Access to a device that can open https://rentahuman.ai/qa

Task

Test both RentAHuman conversion funnels end to end as a genuinely new user, using a clean browser profile or incognito window with no RentAHuman cookies or active session. Record the complete test with screen and microphone and narrate expectations, confusion, trust concerns, and perceived friction. Never expose passwords, OTPs, recovery codes, card numbers, billing addresses, private messages, or other sensitive information; pause or obscure credential and payment entry, then resume immediately. PART A — /qa free-review funnel: Open https://rentahuman.ai/qa from a clean state. Explain what you think the offer is. Enter https://rentahuman.ai as the public website to review, wait for the AI-generated review plan, and assess whether it is specific and useful. Click the primary free-review action, create a genuinely new account using an identity you control, claim the free review, and verify Run History opens automatically and shows the new run with an accurate status. Confirm no card is requested for the free review. If the review completes during the task window, open its report and recording; otherwise document its current state and whether the next step is understandable. PART B — main requester and real-payment funnel: Return to https://rentahuman.ai and approach it as a first-time customer. Find the primary path for posting a bounty. Create a real public bounty asking one person to take and submit a current photo of the sky; keep the task lawful, location-independent, and free of private information. Use a real payment method you control to fund the bounty, with all payment details hidden from the recording. Verify the charge/funding succeeds, the bounty appears in the expected requester dashboard or live state, and the amount/status/next steps are clear. Then cancel the bounty, verify cancellation succeeds, and verify and document exactly where the refunded funds go and what refund status or timing the interface promises. Do not accept an applicant or let anyone perform the sky-photo task. If cancellation is temporarily unavailable, stop and document the blocker rather than creating another bounty or spending more. Submit the bounty URL or ID, visible non-sensitive payment/funding confirmation, cancellation confirmation, and refund destination/status. For every error or blocker, record the exact step, URL, visible message, expected result, actual result, and whether one retry changes it. End with: stage-by-stage pass/fail for both funnels; the three highest-impact conversion problems; anything that appears broken; whether you would trust the service enough to buy again; and specific copy, interaction, or design changes that would improve conversion.

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 512 MB, plus at least one representative screenshot.
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.