We are so happy you have decided to join our tester community!
This quick start guide is meant to cover the basics and to enable you to be successful in the onboarding course.
Detailed information can also be found in various sections of our Tester Academy.
Let's have a look at your tester dashboard since this is the first thing you see after signing up or logging in to your account. First and foremost, in the left navigation bar, you can find the tests that you participated in or that are currently running; they are either currently running or ended but have not been fully reviewed by the customer.
Your tester dashboard is also the right place to view unread comments, edit your data and contact information. You can read more about your tester dashboard in the respective article.
In order to get your Test IO career going, the first thing you need to do is complete Onboarding courses. They can be found on your dashboard. These courses will teach you a lot of basics that you will need to know for the tasks. More information about each course can be found when you start them!
Here at Test IO, we run different types of tests and, depending on the type of the test, you should adopt different testing methods and techniques. We normally use the following terms:
Test Overview Page
Every test on our platform has a test overview page that you can access right after you receive the invitation email – even if the test hasn't started yet. Here, you can find all important information about the scope of the test including features, instructions, known bugs, payout of bug reports, and much more.
Read more about our test process here.
Submitting a Bug Report
After you have tested the given website or app and found a bug that is in scope, you now need to document your findings in a proper and consistent way. To do so, fill in a bug form that consists of the following sections and submit the report:
Bug Report Title
Steps to Reproduce
Before submitting a bug report, please make sure to read the article Bug Report Requirements and make sure that your bug report meets our quality standards. Low-quality bug reports will be rejected.
A bug is a software-related problem. If something on a website or in an application does not work as it was intended to, this “error” is called a bug. Here at Test IO we use the following categorization:
More information about different bug types can be found in the linked articles above.
For more information about the onboarding process and tips on how to find bugs in your first test, please visit the corresponding Academy article – Onboarding tips.