"Our Academy will be your best friend in your journey, so please take your time to navigate through it and increase your knowledge about how to test."


Table of contents


Motivation

If you are an experienced tester or if Test IO is your first-ever experience with crowd-testing platforms, we have a selection of topics that will help guide you through the process of testing a product. Although the tester job might seem difficult at first, don't feel discouraged and remember that you will only get better with time. Our Academy will be your best friend in your journey, so please take your time to navigate through it and increase your knowledge about how to test.

Test Process

Test cycles are small projects created by our customers in order to test one of their products in a particular state or version. You will be regularly invited to these cycles and you can either accept or reject the invitation. If you decide to accept it, you will then be part of the testers team of that cycle and will be paid to submit valid tasks, such as Bug Reports, User Stories and Bug Reproductions. For more information, please visit this link.

Testing Environment

The testing environment is a version of the app or website that should be tested by you, provided and maintained by the customer. However, a customer can have multiple environments available (such as Live, Staging or Beta ones) and you must always be careful to test only the ones that were suggested by the instructions of the cycle. Testing a different environment can cause your bugs to be rejected or even harder punishments for you in our platform, so pay attention to the instructions to avoid making mistakes. For more information, please visit this link.

Test Scope

The scope of a test defines what areas of a customer's product are supposed to get tested, what functionalities to focus on, what bug types the customer is interested in, and what areas or features should not be tested by any means. The scope of the cycle can be found in the test instructions and is formed by many information such as the terms of the test, the testing environment, the cycle instructions (which include sections such as "Goal of this test", "Out of scope" and "Additional requirements"), the features, the bug types and severities, the cycle attachments, the requested devices, the "Out of Scope" section and the chat information left by the TL or the CSM of the cycle. But be careful because some problems (such as setup issues) will always be out of the scope of our cycles. For more information, please visit this link.



Did this answer your question?