I need a reliable and detail-oriented QA tester for a web platform that includes registration, login, Stripe payments (sandbox), a booking system, transactional emails, multi-language support (8 languages), and multiple user roles.
This is a real, complex system — not a brochure site. I need someone who thinks like an end user and catches issues that matter.
TEST DAY: Tuesday, March 31st
Testing window: 10:00 → 19:00 CEST (Geneva, Switzerland — UTC+2)
You may work any time within this window. The test itself takes 2–3 hours — the 9-hour window gives flexibility across different time zones. All deliverables must be submitted by 19:00 CEST.
Scope of work:
- End-to-end flows for all user roles (customer, Avatar)
- Stripe payment flows: success, 3D Secure, declined, expired card, insufficient funds
- Email testing: delivery speed, content accuracy, correct language per user role
- Multi-language UI: 8 languages, full flow tested in each
- Mobile testing: iPhone and Android — full booking and payment flow
- UX review: identify where real users get confused or stuck
- Avatar system: booking notifications, accept/decline, dashboard, real-time
Deliverables (all due by 19:00 CEST on March 31st):
- Completed checklist (provided — detailed and structured)
- Screenshot for every flagged item, named and organised in a folder
- Full session Loom recording (or equivalent)
- Bug report with priority levels: blocking / major / minor
- Summary email: top 3 critical issues found
Budget:
- Cycle 1 (March 31st): $50–70
- Cycles 2 & 3: $30–40 each — dates confirmed after bug validation and fixes from the previous cycle
- Total: up to $150 for full engagement
To apply, please answer all 4 questions — proposals without answers will not be reviewed:
1. Describe a Stripe payment test you ran. What did you test and what did you find?
2. Walk me through how you would test a booking cancellation flow.
3. If a user pays for an additional service (like content creation) but the provider never receives the request — how would you detect and report that issue?
4. What is your process for organising screenshots and recording sessions during a test cycle?
Please confirm in your proposal that you are available on Tuesday March 31st and can deliver by 19:00 CEST.
No generic proposals. I read every answer carefully.
... Show more