QA test: QA: English speaking check (Oruk B2) on a test bounty — 2026-09-16

Before you apply

• Access to a device that can open https://rentahuman.ai/bounties/c4d6e3a91d91279669f1
• Laptop or desktop browser with a working microphone
• Can record the screen with spoken narration
• Own Rent A Human worker account (no shared or team accounts)

Task

One-time QA of the NEW English speaking check that some Rent A Human bounties now require before you can apply. The target is an internal test bounty owned by the Rent A Human team: your only job is to try to APPLY to it and record what happens. Do not perform any work for the target bounty; it will never accept your application. You are paid by this QA run for an honest, complete, evidence-backed report, whether the check passes, fails, or errors. Use a laptop or desktop browser with a working microphone (Chrome, Edge, Safari or Firefox; say which). Record your screen with spoken narration for the whole session (about 5-10 minutes). You may blur or avoid showing your email, phone or other private profile details. Journey: 1. Signed in to your own Rent A Human worker account, open the target bounty. Read the page and show where it says an English speaking check (B2 or higher) is required, then click Apply and show the explanation screen before recording. 2. Start the check and allow microphone access. While the ~45-second recording is running, CLOSE or cancel the dialog before it finishes. Show that recording stopped (browser microphone indicator off) and that no result and no application appeared. 3. Click Apply again and this time complete the full recording. Speak spontaneously in your own English (for example, describe your day or a hobby). Do not read a script and do not include private information. Wait for the result and show the exact screen: passed, below the required level, try again, or an error. Say how many seconds it took after the recording ended. 4. Follow what the screen offers. If it says passed, continue and submit the application with the cover letter: QA test - please do not accept. If it says below level, try again, or error, show the message, use the offered retry once if there is one, and show whether you can still apply. If the check says you already passed earlier (level reused), say so on camera and continue. 5. Reload the bounty page once more and show what state the check/apply button is in now. Written report: browser name and version, operating system and device, microphone type, the exact result text shown (CEFR level if any), seconds to result, any confusing wording, every error, and short reproduction steps for each issue. A clean pass with no issues is a valid, fully paid result.

Submission requirements

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

1. 1Requirement shown on bounty page and before recordingShow where the target bounty page says an English speaking check (B2 or higher) is required, then click Apply and show the explanation screen that appears before any recording starts.
2. 2Cancel mid-recording stops the mic and submits nothingStart the check, allow microphone access, and close or cancel the dialog before the ~45-second recording finishes. Show that the browser microphone indicator turns off and that no result screen and no application appeared.
3. 3Complete a full recording and show the exact resultApply again, complete the full recording speaking spontaneously in your own English (no script, no private details), and show the exact result screen: passed, below level, try again, or error. State how many seconds it took after the recording ended. Any honest outcome counts.
4. 4Follow the result: apply, retry, or blockedIf passed, continue and submit the application with cover letter 'QA test - please do not accept'. If below level, try again, or error, show the message, use the offered retry once if available, and show whether Apply is still blocked. If the check says you already passed earlier, say so and continue.
5. 5Written report with device details and repro stepsReport browser name and version, OS and device, microphone type, exact result text (CEFR level if shown), seconds to result, confusing wording, every error, and short reproduction steps for each issue. A clean pass is a valid result.
6. 6Complete the assigned test stepsFollow every instruction above. If a step is blocked, name the exact step and explain what prevented it.
7. 7Describe test coverageList the steps, pages, controls, devices, and paths you actually tested.
8. 8Report concrete resultsExplain what happened, what worked, and any confusing or poor experience you observed.
9. 9Provide the required video evidenceAttach an MP4, MOV, or WebM screen recording no larger than 512 MB, plus at least one representative screenshot.
10. 10Map 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.
11. 11Make every issue reproducibleFor each issue, include a short title, severity, expected behavior, actual behavior, and exact reproduction steps.
12. 12Still report useful observations if nothing failedA no-issue result must still say exactly what you tested and include concrete usability observations.