Skip to main content

Test IO Testing Standards

Zorica Micanovic avatar
Written by Zorica Micanovic
Updated over a week ago

What We Expect From You on the Platform

We want you to succeed on Test IO — and to help you do that, we’re sharing some clear expectations.

1. Performance

  • Keep your bug acceptance rate above 50%

  • We take into consideration your contributions over the past 60 days

  • If it stays below 50% for the recent activities, the Compliance Team may reject your account

  • From the moment you join Test IO, your journey begins with a probation period. During this phase, we assess how well you learn, follow test instructions, and meet Test IO’s quality standards. If your recent activity does not align with these expectations, the Compliance Team may take appropriate action, including account rejection.

2. Professional Conduct

  • Be respectful in test chats, bug comments, Discord, and support

  • Read and follow test instructions carefully to avoid mistakes, warnings, or bans

  • Join only if you plan to test — if you can’t participate, leave the cycle so others can join

3. Do

  • Understand the scope: Read feature descriptions and the test brief before starting

  • Collaborate: Ask for help when needed and support others

  • Report reliable bugs: Only submit issues you can reproduce; confirming others’ bugs improves quality

4. Don’t

  • Use automated tools (scripts, VMs, emulators) that compromise integrity

  • Be abusive or harass anyone

  • Rewrite known bugs to pass them as new

  • Submit placeholder or incomplete bug reports

  • Create multiple accounts

  • Submit non-reproducible bugs

  • Ignore device/browser requirements — use what the test specifies

Did this answer your question?