Introduction
Welcome to Test IO's Greenhorn Tests! If you're new to the platform with fewer than 50 submitted bugs, these voluntary training tests are specifically designed for you. Greenhorn Tests provide a supportive learning environment where you can practice Test IO's bug-reporting standards, platform processes, and best practices on websites we've selected for training purposes. These are not customer projects - they're dedicated training exercises to help you develop your skills before participating in actual customer tests.
Participation is entirely voluntary and at your discretion.
Testers who actively participate in Greenhorn test cycles …
Are 57% more likely to reach the Bronze or a higher level.
Have a 7 percentage point higher Bug Approval Rate.
Receive 3x as often a Bug Like from a TL or customer.
Earn 19% more per submitted bug, highlighting that more severe bugs are found.
What Are Greenhorn Tests?
Greenhorn Tests are exploratory training exercises available to new testers across all regions. These tests differ from regular customer tests in one key aspect: these are dedicated training scenarios, not actual customer projects. Test IO reviews your reports, reproductions, and user stories as part of the learning process, with a focus on the quality of your bug documentation and helping you master our standards rather than identifying defects for external clients.
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.
Stages of Greenhorn Tests
At Test IO, Greenhorn Tests are divided into three stages, each designed to progressively develop your skills as a tester:
"Web Basics & Observation (eCommerce)" tests are tailored for beginners who are just starting their journey at Test IO. The objective is to introduce exploratory testing, basic web testing concepts, and observation skills on a simple e-commerce platform, while helping testers become familiar with the Test IO interface.
Tasks in focus:
Identify and report visual/content issues in Homepage, PDPs, PLPs, & Cart.
Create proper screenshots with highlights of issues.
Use the test chat interface (send an initial ❝Hi❞ message).
Practice basic test chat tagging and using @chatBob for troubleshooting or general questions.
Identification of duplicated bug reports by using the Known bugs and similar issues features.
"Full Bug Type Reporting" is the second wave of tests that becomes available as testers progress within Test IO. Its objective is to develop comprehensive bug reporting skills across different types of issues.
Tasks in focus:
Report content, visual and functional issues with clear reproduction steps.
Prioritize bugs within a specific feature flow based on feature description to help testers focus on feature identification and test scope boundaries.
Create proper screencast documentation.
Apply basic testing techniques using disposable emails, cache, and cookie clearing for clean testing sessions.
"Exploratory Testing with Tools (Mobile Web)" refers to the final test of the Greenhorn journey. Its objective is to introduce mobile web testing concepts while covering all types of bug submission in exploratory testing.
Tasks in focus:
Test common user journeys on mobile web browsers.
Use proxy tools or VPNs to test different locations/conditions.
Document mobile-specific issues (responsive design problems, touch interactions).
Test under various mobile conditions.
Execute user stories for mobile web testing.
Bugs submitted in Greenhorn Test Cycles count towards your Tester Level system (the same as bugs in Customer tests), helping you level up and showcase your skills.
Key Features of Greenhorn Tests
Eligibility: Available to testers with 50 or fewer accepted bugs 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 bug type report (content, visual, or functional) open (with "Awaiting Review" status) at a time. You must wait until your current reports are 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 reports before creating another
Helps you apply new knowledge immediately to your next submissions
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, 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!