TEST.IO Review Website Tester Jobs Online

When you are looking for online website tester jobs then TEST.IO must be part of your list of companies to register with because TEST.IO will send you many invites and opportunities earning money online testing web sites and apps, this TEST.IO Review show the ins and outs of TEST.IO and then it is for you to decide to join them or leave it as is.

You do not need to have experience in website testing although obviously if you have any you will benefit from that experience and you will get more jobs from TEST.IO to test websites and apps.

Unfortunately, they not always pay, despite being in close email contact and not clear in what they want. You can read this review which on its own is positive but be aware that it will happen that they do not pay you, it happened to me, so be warned.


If you want to be a website tester, TEST.IO will have enough website tester jobs for you to stay occupied for a long time to come. And not only websites more and more apps for iOS and Android will need to be tested and that is only a fraction of what is coming. Mobile phonisre becoming more and more important in our lives and with that come apps and they all need to be tested.


Working from home, sometimes to late at night, in only a few days I have done several tests and if you are serious to become a website tester from home and are on the lookout for interesting website tester jobs then register yourself at TEST.IO.


What is TEST.IO?

test IO LogoTEST.IO is a Germany-based company has set up a software test platform where customers can totally independent setup a test or staging environment and have crowd testers test their software on functionality or bugs.


From the TEST.IO point of view they obvious look at their customers first, at the end, they bring the money but on the other hand, customers do not have 20,000 testers available testing their software in just a couple of hours. And that is what TEST.IO brings a large platform where customers can have their websites and apps tested using a large workforce of 20,000 testers which is increasing on a daily basis.


I will not go into the technical detail how customers can use the Jira API to connect their test environment to the TEST.IO environment because for you as a tester that is less important.


You, and me, just want to see the tests coming and execute these tasks, report so the customer can take the reports into account and make their application better.


Excepting a Test

I joined in August 2016 and have seen many tests passing by, I had to decline a few because I could not do all and sometimes I had problems with my iPhone. Is that a bug? Well, more at my site so I declined with technical issues.
But after a decline, new invites are sent to my email account and then make sure that you are quick to react and accept the invitation.


Customers do not need 20,000 people, they want only a few users and that can be 10 or 20 but that means that once all places are occupied you cannot accept the test anymore.


Declining an Invite

Now you also understand that I decline sometimes when I just cannot do the test. I lose my place but that is okay, it is better to decline than to leave it as is, keeping the place occupied and not executing the test.



Every tester is evaluated and that means when you do not decline but at the same time you do not execute the test you will get a bad name and fewer jobs will come to you.


Point of View

Obvious I look from the testers point of view, at the end you want to earn money online and testing websites and apps is an excellent idea, to me it is a better idea than clicking advertisements in PTC sites or doing surveys but okay, that is me, not everyone likes to test websites, testing websites and apps help companies to make their product better and that is what we all want isn’t it?


Read the SCOPE

Before you start any test read the scope of the test. You might see a bug but if the bug is found in an area that is not in scope then your submitted bug report will be rejected. From the customer point of view, I can understand, they only want to test a certain area but for you as a tester you see a bug and report on it.


Example where my Bug Report was Rejected

Let me give you an example, during the testing of a website the customer specifically asked for errors however when I went to the page describing their mobile app the main menu was gone. Clearly a bug but as it did not give an error, it was not in scope. I submitted it as a bug but because there was no error message it was not in scope and therefore rejected.


Of course, it is a bug, very irritating for the visitor of the website but what can you do? Well, read the instructions clearly and keep the bug reporting to the scope. It is the quality, not the quantity the customer is after.


Every bug that you find and is in scope will need to be reported in a certain format and that includes the exact path from the homepage you took to get to that bug. There are guidelines to make sure that your report is of the highest standard and not just a piece of crap. It is not that you and I are the best testers in this word, we are not, but having a clear way of reporting makes it easier for the developers to understand the problem and see what happens before they start solving the issues.

Screenshots & Video

keyboard phone

If you find a bug, submit a screenshot so it is clear to see what the problem is. A video definitely will help. Showing how you got to the bug in a video and talk what you do because it might be that you do something stupid and only because of that stupidity the bug was seen.



Describe the path in words and show it in a video, that means that the bug must be reproducible. When I find a bug I go back to the home page, switch on the screen recording and do exactly the steps to get to the bug.


Next step is that the video must be in MP4 format and uploaded, this gives time to describe the bug in the reporting format they would like to have and once the MP4 video is ready I upload this video and submit the bug.


Time and Money

This all takes time. Is it worth the money? Well, yes and no, if you spend a couple of hours testing and earning maybe €10 and then finding out that some “bugs” are rejected because they were out of scope, then you might say it is not worth it.


However, you learn from the tests, same as I do, and from that learning, you also will learn how to find the critical bugs, these pay a lot higher than the low and high-risk bugs. The critical bugs are the bugs that crash the application.


Two typical payout schedules and it all.


TEST.IO Payout

In the table to the right clearly, you will get paid for usability and that means that you will need to create a video and talk while you are going through the website. If you compare this sites like Whatuserdo then it is low, where Whatusersdo will pay £8 for a usability test this customer at TEST.IO will pay €2.00

On the other hand, you will get paid €10.00 when you find a critical bug where at Whatusersdo you most likely do not get critical bugs because they have more or less only usability testing.


TEST.IO Payout

The Payout schedule on the right shows that a lot less will be paid so you might think that you will not even accept this offer, that is for you to decide. If you do not test, others will, it is just that simple but I would recommend doing any test so you learn how to test and how to report.




In order to get payment directly in your bank account, Paypal or Skrill you do need an EU VAT ID which you should be able to obtain through your local TAX Authorities. This is needed, without this ID you will not be paid.


TEST.IO is based in Germany and the German law just insists that everyone working for a Germany company and is part of the EU will send their EU VAT ID. 


Once you have received this VAT ID then you have to fill that into the payment section.


Hint: Place the code of your country in front of the VAT ID itself.


I am in the UK so had to place GB in front of the VAT ID I received from the HMRC, nobody is telling you that.


Once done you can choose to have the payment sent straight into your bank, Paypal and Skrill. I do not need to say that when you use Paypal you will pay a small commission on to Paypal earning you even less.


I do not know Skrill and will not use them myself, but maybe you have an account already and then it might be useful to get your money into your Skill account instead of your Paypal or personal retail bank account.



TEST.IO used to be good but I cannot recommend them anymore. You can do a lot of work and not get paid only because their requirements are not clear. Yes, you can earn money but the fact that you need a VAT ID, the fact that they do not pay you, I would say check out other sites that do pay.



TEST.IO is not the only company where you can test websites and apps, there are a lot more and although not all are good there are a few that are definitely worth to join like Utest Review, Whatusersdo Review and TryMyUi Review.


Usability Testing

If you are more in usability testing then check out Userfeel Review or Usertesting Review which might be good TEST.IO alternatives to bug testing.



If you are not in website testing, then I assume that you went from the top of the page straight to the bottom otherwise you have been reading for some time now in this article only to find out that you might be more interested in the alternatives rather than becoming a website tester.


Looking at alternatives, it basically comes down to what you want. Do you like to click for pennies, do you like to do surveys for a little bit of money, do you want to start your own business, become a freelancer or write your own blog.


If you are unsure why not contact me and have a chat about what might be good for you.