We are so happy you have decided to join our tester community!

This quick start guide is meant to cover the basics, so you pass the onboarding quiz and onboarding tests, and start testing in customer projects.

Detailed information can also be found in various sections of our Tester Academy.

Your Dashboard

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 participate or participated in; 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.

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.

Onboarding Tests

If you are a new tester at test IO, the first test you will be able to participate in is an onboarding test. This test is your chance to learn the basics and understand the platform. With these tests, we ensure that only qualified testers enter customer tests. 

Before you can practice in live testing, you first have to pass the onboarding quiz that consists of 12 questions and which covers the basics of our testing procedures. You need to have at least 8 correct answers to qualify for the practical part – our onboarding tests. Don't worry if you don't pass the quiz on the first attempt – make sure to read through all the articles of our Academy and give it another try. 

For more information about onboarding tests, please visit our corresponding article

Test Types

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: 

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

  • Expected Result

  • Actual Result

  • Attachments

  • Environment

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.

Bug Types

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 how to find bugs in your first test, please visit the corresponding Academy article - Onboarding tips

Did this answer your question?