We are extremely happy to have the opportunity to work with you. Since this is your first workspace invite, we want to make sure things run smoothly for you and that you have all the information you need.

Did you sign up but didn't get any emails from us? It’s probably because they are in your junk folder. To avoid this in the future, we have a guide for you on how to receive emails from Testlio.

Keep in mind that we at Testlio pay our freelancers by the hour (not by the bug). This produces the best freelancer experience and the best results for our clients. Payments are done weekly via PayPal or Payoneer.

Please note that if you see an amount of $0 for your approved tasks, this does not mean that you will not be paid! The amount will be adjusted the latest by Thursday evening (timezone: CET) with the correct sum.

As you might have noticed, after receiving a workspace invitation, you also got an invitation to a Test Run. If you still haven’t gotten a Run invitation, don’t worry, you just need to wait until you receive one. It may take some time.

On the Run invitation, you can see when this particular Run is active, as well as the amount of time you have been allocated to test in this Run. This is a crucial point for new testers since it is expected that all testers complete the amount of testing they were allocated before the end time for the Run.

Example:

We'd like you to test for:

2.5 hours

You will also see what kind of devices we expect you to use while testing in this particular Test Run, based on the listed devices under your profile. If you don’t have the device available for testing or your OS version is updated to a newer one, please do not accept the run invite. Instead, update your listed devices.

Example:

We expect you to test with:

Apple MacBook Pro 2024 13" macOS Sonoma 14.5 using browsers: Safari

Last but not least, you will also see when the Run is active in your listed timezone, which means that you can evaluate whether you can participate in this Run or not.

Example:

The Run is active:

from Thu, 15 Aug @ 14:00 to Fri, 16 Aug @ 12:00 (Europe/Tallinn).

These invitations have a huge impact on how we operate at Testlio, this is why we would like to kindly ask you to confirm your participation in the Run with a “Yes” or “No”. This way we can evaluate the total needed testers for the Run. If you say "Yes", please remember that you are required to complete the task by the agreed deadline and with the agreed device configuration. If you say “No”, don’t worry, we respect your free time and this will not negatively impact your rating.

If you have confirmed your participation with “Yes” but for some reason cannot take part in the Run, please make sure to let the Test Lead (Coordinator) know as soon as possible. This way we can find a replacement and make sure the Run will proceed without issues. Not reaching out to the team may result in incident being reported and impact your rating negatively.

Always inform the Test Lead (Coordinator) in advance if you feel that the Run execution will take more time than initially allocated. Before going to spend more time on the given task, it needs to be agreed with the Test Lead.
​Please, always use the full time that we have allocated to you. If for some reason, you finish testing earlier, we suggest you go through your results once again and explore around. If you use significantly less time than allocated (i.e. less than 0.9x of the estimated allocation), please definitely notify the Test Lead.

P.S. If you have a rooted device, make sure you let the Test Lead (Coordinator) know before going into testing. Otherwise, there may be a situation where you are unable to test a specific app with a rooted device and this will affect the results for both you and the customer.

The reason we have pointed out the following Help Center articles is that we want you to succeed. Please read them carefully.

Testing depends a lot on time management. This is why we recommend you read our Services team's tips about time management.

Keep this Glossary of QA terms close to you while testing in case you are not familiar with all the QA terms we use at Testlio.

You are presented with the Instructions to testers. This is the most specific part of your testing guidelines that will be also displayed for you on the left sidebar throughout the run. For any tester, attention to detail is a must-have trait. At Testlio, we expect all our testers to follow instructions and guidelines about the run's scope and objectives.

To understand what is expected from you, you should make sure you read all the instructions carefully.

You are asked to download any necessary builds. Check the Downloading Builds section for instructions.
​
Here you can also see what type of device you are expected to test with. Please do not change it without consulting with the Test Lead first. In some cases, you might not be allocated a device, so you can click on the three dot icon and declare the device that you are using for testing in this Run.

Note: If you don't have the device and OS-version combination that is needed for this testing, please let the Test Lead know as soon as possible.

After you have clicked Go testing, you see your test plan view.

Example of a test plan view:

A good idea would be to read through all the steps once so that you familiarize yourself with the plan. Afterwards, you may start testing. Please make sure that you go through the steps one by one, as marking them as passed, failed or blocked in bulk may cause you to miss certain issues.

Read a more thorough article about how to fill out a test plan.

Throughout the Run, you can see on the top right corner, there is a red “Stop testing” button. You can pause your testing by clicking on this button. You will be able to resume your testing until the Run end time and date.

1. Make sure it is not a duplicate.

While you are going through the test and something has failed to work as it should, you may have stumbled upon an issue (bug). Before you create a new issue, make sure it is not a duplicate. You can read a more thorough article on how to look for duplicates here.

After marking this step as 'Fail', you will be presented with the 'Issue browser' view.

Under ‘In this step’ you will be able to see issues that have already been filed in the same step that you are at the moment. If you find an issue that is already reported, do not report it again but perform a reproduction to this issue instead.

Click on the green 'Reproduced' button, fill in the environment details, add attachments, and click 'Submit'.

Please note that in every new Run, you only need to add your environment details once to perform a reproduction. Meaning, if you encounter another duplicate later on in this test plan, you can simply mark the check box that says 'I have provided my environment details. Link issue without a new reproduction environment comment.' -> click 'Submit'. This way you can skip adding another reproduction comment under the issue.

Note: Reporting duplicates may negatively impact your rating.

2. Create a new issue

If you have made sure that the issue you have found isn’t reported yet, you can report it as a new issue by clicking on the blue ‘+ New issue’ button.

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, a descriptive title that describes the issue a little more.

Read a more thorough article about reporting issues.

After you have finished testing, you will also have an option to give feedback on the Run. We love to hear your honest and candid comments, no need to worry about “wrong” answers since there’s no such thing. Your feedback helps us evaluate and plan future testing Runs better.

Communication is the key to successful Run collaborations. Please ask questions if you need help. We strongly encourage you to always ask questions, there are no wrong ones. Also, we kindly remind you that helping others would be super sweet of you as well. Team is everything!