Issue Acceptance
After each run, our team of Test Leads and Testing Coordinators approve or close issues that have been raised. Issues that are closed with certain reasons are counted as not accepted and negatively affect your rating.
By closely following the guidelines which are provided for each run, you can ensure that all your issues are up to standards. The pillars for raising issues that matter are:
Reading the instructions and workspace guidelines
Familiarizing yourself with out of scope areas
Checking for duplicates before reporting
Critical thinking is also key. Ask yourself if an issue should be fixed by understanding the purpose of the products and target audience.
Finally, if your issues get closed without approval, use this feedback in future runs. Understanding why it happened will help you avoid making similar mistakes in the future.
Run Attendance
Make sure that you complete all of the runs that you have accepted. We highly encourage testers to keep an eye on their workload. Do not accept a new run invite if your schedule is hectic. Time management is essential.
High Priority Issues
Not all runs are the same, so understanding the purpose of each helps you look for issues. Clients may be asking us to check new areas, or areas that have changed, and it’s likely that you’ll find new issues.
These are known as high priority issues, and it’s important to look closely for them. Exploring around the test steps may uncover them.
Make sure you also understand the business case behind the application so that you can test while thinking of real-life scenarios.
How will users use these features?
What can they expect?
By answering these questions you’ll find high priority issues more easily.
Respond to Invites
Whenever you receive an invite from us, make sure to give us a response. Declining an invite does not affect your rating negatively. We respect your free time and encourage you to take time for yourself in between testing.
Issues per Hour
We want to ensure that we spot as many issues as we can during runs. To do so, testers are expected to understand the applications they are testing, which may include looking deeply into error-prone areas.
Exploring around test steps will help you detect issues that may have otherwise been harder to find.
Read more about various testing types and approaches to stay on top of testing techniques.
Starting your testing run as early as possible helps you increase your issues per hour and find high priority issues faster.
#TestlioBot