Manual Testing Specialists Wanted
Budget: $15 – $25 USD
I need a small team of detail-oriented manual testers to put our in-house builds through their paces. You will explore each feature exactly as an end-user would, log every defect with clear reproduction steps, screenshots or screen-recordings, and assign an appropriate severity. Because the products span web, mobile, and a lightweight desktop client, your own device mix is welcome—just tell me upfront what hardware and OS versions you can cover.
Here’s how we’ll work together
• You receive the latest build, access credentials, and a short onboarding video.
• You create or update test cases in TestRail (or your preferred equivalent) and execute them.
• During exploratory passes you note functional glitches, usability snags, and any obvious performance slow-downs; no automated scripts are required.
• All findings are filed in Jira with labels, screenshots, and a quick Loom video when visuals help.
• A concise test summary closes each cycle so the dev team sees overall quality at a glance.
Acceptance criteria
1. Every reported issue includes reproducible steps, environment details, and evidence (image or video).
2. Test case execution sheet shows PASS/FAIL results for every scenario supplied.
3. Final summary highlights critical blockers, major usability concerns, and areas retested after fixes.
If you are comfortable switching between browsers, real devices, and virtual machines—and you enjoy hunting for edge-cases—I’d love to start a short paid trial. Turnaround for the first round is 48 hours once you have the build.
Here’s how we’ll work together
• You receive the latest build, access credentials, and a short onboarding video.
• You create or update test cases in TestRail (or your preferred equivalent) and execute them.
• During exploratory passes you note functional glitches, usability snags, and any obvious performance slow-downs; no automated scripts are required.
• All findings are filed in Jira with labels, screenshots, and a quick Loom video when visuals help.
• A concise test summary closes each cycle so the dev team sees overall quality at a glance.
Acceptance criteria
1. Every reported issue includes reproducible steps, environment details, and evidence (image or video).
2. Test case execution sheet shows PASS/FAIL results for every scenario supplied.
3. Final summary highlights critical blockers, major usability concerns, and areas retested after fixes.
If you are comfortable switching between browsers, real devices, and virtual machines—and you enjoy hunting for edge-cases—I’d love to start a short paid trial. Turnaround for the first round is 48 hours once you have the build.
Related categories:
Video Services
Testing / QA
Software Testing
Usability Testing
Regression Testing
Web Testing