AllComputer GigsCreative GigsCrew GigsDomestic GigsEvent GigsLabor GigsTalent GigsWriting Gigs
QA test: website first-time user test — 2026-09-17
Estimated duration
~1h
Deadline
Tue, Sep 22, 2026
Location
Remote only
•
PRICING
$10 fixed
USD
per approved result
DESCRIPTION
One-time QA test run for https://website/.
Submissions are reviewed automatically. $10.00 is released per accepted submission.
What you must do to be paid
Before you apply
- Access to a device that can open https://website/
Task
https://website/somethings are change like color are old
- Open the product on a mobile-sized screen and narrate what you expect before taking action.
- Complete the primary journey from its entry point through the final confirmation using only a tester-controlled account.
- Repeat any confusing or broken interaction, then record the exact steps and visible result.
Evidence: Submit one narrated screen recording, timestamp every finding, include exact reproduction steps, and rate each issue as low, medium, or high severity. Keep the test to five minutes. Login journeys are supported with a tester-controlled test account. Do not use owner-supplied private credentials, complete a purchase, or make destructive changes.
Submission requirements
Video assignments require spoken microphone narration throughout. Captions, written narration, and on-screen text are not substitutes.
- 1Complete the assigned test stepsFollow every instruction above. If a step is blocked, name the exact step and explain what prevented it.
- 2Describe test coverageList the steps, pages, controls, devices, and paths you actually tested.
- 3Report concrete resultsExplain what happened, what worked, and any confusing or poor experience you observed.
- 4Provide the required video evidenceAttach an MP4, MOV, or WebM screen recording no larger than 512 MB, plus at least one representative screenshot.
- 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.
- 6Make every issue reproducibleFor each issue, include a short title, severity, expected behavior, actual behavior, and exact reproduction steps.
- 7Still report useful observations if nothing failedA no-issue result must still say exactly what you tested and include concrete usability observations.
REQUIREMENTS
- •
Only submit evidence you captured yourself during this run