Introduction
Welcome to Test IO's Greenhorn Tests! If you're new to the platform with fewer than 50 accepted bugs or 100 accepted bug report reproductions, these tests are specifically designed for you. Greenhorn Tests provides a supportive environment where you can learn Test IO's bug-reporting standards, platform processes, and best practices before diving into customer tests.
What Are Greenhorn Tests?
Greenhorn Tests are exploratory tests available to new testers across all regions. These tests differ from regular customer tests in one key aspect: Test IO is the customer. This means Test IO accepts reports, reproductions, and user stories, with a focus on the quality of your bug documentation rather than just the defect itself.
The primary goal of these tests is educational—to help you understand Test IO's requirements, rules, and processes while providing you with constructive feedback to improve your testing skills.
Key Features of Greenhorn Tests
Eligibility: Available to testers with 50 or fewer accepted bugs OR 100 or fewer accepted bug report reproductions on the platform.
Regional Availability: Tests are divided by regions: DACH, the United States, India, Vietnam, and the rest of the world.
One-at-a-Time Submission: You can only have one report open (with "Awaiting Review" status) at a time. You must wait until your current report is closed (accepted or rejected) before submitting another one.
Dedicated Team Leaders: Greenhorn Tests are managed by specialized Team Leaders who focus on educational feedback rather than just bug triaging.
The One-at-a-Time Rule Explained
The one-at-a-time submission policy exists for an important reason: it allows you to learn from each submission before moving on to the next one. This approach:
Ensures you receive feedback on one report before creating another
Helps you apply new knowledge immediately to your next submission
Creates a gradual learning curve that builds your skills systematically
Prevents common mistakes from being repeated across multiple reports
What Team Leaders Look For
Greenhorn Team Leaders review your submissions with an educational perspective. Here's what they will evaluate, but not only, in your bug reports:
Title
Does it answer the three essential questions: What, Where, When?
Is it clear and descriptive?
Feature Selection
Have you correctly identified which feature the bug relates to?
Severity Assessment
Have you assigned the appropriate severity level to functional bugs?
Have you followed any pre-assigned severity guidelines?
URL and Steps to Reproduce
Is the URL complete and correct?
Does the first step include the corresponding URL?
Are the steps comprehensive (including necessary credentials when required)?
Does the last step accurately trigger or lead to the bug?
Actual and Expected Results
Are these sections clearly differentiated?
Do they avoid simply repeating the steps or title?
Do they clearly explain what happened versus what should have happened?
Attachments
Are dates formatted correctly?
Are you using the appropriate device/browser?
Is your browser updated?
Are you avoiding VPN use (unless specifically requested)?
Screenshots
Have you properly highlighted the issues?
Did you add the additional screenshot with the current date and time when testing on a mobile device?
Screencasts
Are clicks/touches visible in your recordings?
Did you display the current date and time? Ideally at the beginning, so you never miss showing this mandatory information.
Tips for Success
Read Test Instructions Carefully: Each Greenhorn Test may have specific instructions, such as bug submission limits or out-of-scope areas.
Communicate in the Test Chat: If you have questions, ask them in the Test Chat. Team Leaders are there to help.
Respond to Information Requests: When Team Leaders request additional information, respond promptly with the requested details.
Study Academy Resources: Team Leaders will often reference Academy articles in their feedback. Take time to read these resources to improve your understanding.
Be Patient: Remember that feedback is meant to help you grow as a tester. Take the time to understand and apply it.
Quality Over Quantity: Focus on submitting well-documented, high-quality bug reports rather than trying to submit many reports quickly (Get inspired by these bug report examples collection).
What Happens After Greenhorn Tests?
After successfully participating in Greenhorn Tests and reaching more than 50 accepted bugs or 100 accepted bug report reproductions, you'll graduate from the Greenhorn program and be eligible to participate in even more regular customer tests.
The skills and knowledge you gain during Greenhorn Tests will be invaluable as you progress to customer tests, where the stakes are higher but the reporting standards remain the same.
Conclusion
Greenhorn Tests is your training ground—a safe space to learn, make mistakes, and improve before entering the world of customer tests. Embrace the feedback you receive, apply it diligently to your subsequent submissions, and you'll quickly develop the skills needed to succeed as a valuable Test IO tester.
Remember, every experienced tester and team leader on the platform was once a Greenhorn too. The journey of becoming an expert tester begins with mastering the fundamentals of excellent bug reporting.
Happy testing!