Padel Tournament Site QA
Budget: €6 – €12 EUR
I have a freshly built web platform that lets clubs and admins create and manage padel tournaments. Before launch I need a meticulous round of functionality testing aimed squarely at the tournament-creation workflow.
If you are a padel or tennis player that are used to tournaments, it is a massive plus.
Scope
– Focus exclusively on tournament creation and management.
– Dive deep into event setup and configuration, bracket generation and updates, and score reporting & tracking.
– The critical path I want bullet-proof is everything that happens after an organiser clicks “Create Tournament” until the tournament is finished
- Design optimization (alignments, etc)
What I expect from you
• Systematic test cases that cover normal, edge, and failure scenarios for the three areas above.
• A consolidated defect log with severity, clear reproduction steps, screenshots or short Looms, and retest status.
• Actionable best-practice recommendations (UI flow, data validation, error handling, performance flags) so my devs can harden the code rather than just patch bugs.
• A one-page executive summary highlighting top risks and quick-win fixes.
Timeline is flexible if communication stays tight. Looking forward to sending you the link so you can start breaking things—in the best possible way.
If you are a padel or tennis player that are used to tournaments, it is a massive plus.
Scope
– Focus exclusively on tournament creation and management.
– Dive deep into event setup and configuration, bracket generation and updates, and score reporting & tracking.
– The critical path I want bullet-proof is everything that happens after an organiser clicks “Create Tournament” until the tournament is finished
- Design optimization (alignments, etc)
What I expect from you
• Systematic test cases that cover normal, edge, and failure scenarios for the three areas above.
• A consolidated defect log with severity, clear reproduction steps, screenshots or short Looms, and retest status.
• Actionable best-practice recommendations (UI flow, data validation, error handling, performance flags) so my devs can harden the code rather than just patch bugs.
• A one-page executive summary highlighting top risks and quick-win fixes.
Timeline is flexible if communication stays tight. Looking forward to sending you the link so you can start breaking things—in the best possible way.