Testlio platform is divided into three sections. 

1. Test cycle information
2. Issues (bugs) already reported
3. Chat section, which is used to ask questions from your test leads, project managers or other testers regarding this particular project.

On the test cycle information section, you can see whether the test cycle is active or not. When it is active, there is a possibility to click on the green “Go testing” button, otherwise it is not clickable.

After clicking the green “Go testing” button, you will see the test cycle details that are specific for this cycle, also project details about the client you are testing for:

Example Cycle Details: 

These are all very important details to get familiar with before you start testing. Please make sure to read this page carefully before any test cycle.

If you have read the page, you are good to go and can click again on the green “Got it” button.

On the next page you can go through the test cycle details again and you can also see what  kind of task you are given, how many hours you need to test, and which device you need to use for this particular test cycle.

You can now click “Start” to take part of your very first paid test cycle.

On the next view, you can see on the left there is a task list and on the right there is a testing time, which you can start. Please always keep in mind to start the testing time and use all the testing time that has been allocated to you.

When you are testing

While you are going through the task list and something has failed to work as it should, you may have stumbled upon an issue (bug). In this case, you can click on the blue button “New issue” which is located above the testing time in the right corner.

You then have to enter a clear title into the brackets in which you define the section of the app that is affected, as well as, some descriptive title that describes the issue a little more. 

For example:

[Keyboard] Keyboard didn’t display correctly.

Note: 

Usually the content for the bracketed part of the title will be defined for the project or within the cycle details. 

When entering the title, the platform will now show you related issues (bugs) that have been reported. This will prevent you from reporting duplicates. If that issue exists already, please do not report the issue unless you have been explicitly told to do so. Duplicates cause noise for the test leads, project managers and especially for our clients. Reporting duplicates may negatively impact your tester’s score. Read more about how to look for duplicates here

If your issue(bug) hasn't already been reported, you can report it as a new issue as follows:

1. Evaluate the severity of the issue between low, medium or high. You can hover over them and you can see the description of each severity level.

2. Add a label to it from the right side.

3. Define the affected feature.

4. Define your device that you used when you found the issue (bug).

5. Fill in the new issue (bug) report with “Environment”, “Steps to reproduce”, “Expected result” and “Actual result” information.

See an example of a good issue (bug) report here.

6. Add your log file, mp4 video file and screenshots.

7. Click “Submit new issue”

8. Copy the issue number

9. Go back to tasks list and mark the issue you found as “Fail” and add the issue number to it.

When you are done testing

1. Ensure all test cases have been completed and that all instructions for the test cycle have been done. 

2. End the testing time on your right side of the screen.

3. Submit your tasks list. 

4. Give your honest feedback about the test cycle. This helps us to evaluate and plan future testing cycles better.

Congratulations! You have successfully completed your first paid testing cycle.

Did this answer your question?