test IO Reviews

Test IO banned my account without reason or explanation. I never cheated or violated any rules; I was an active and rule-abiding tester, yet my account was terminated out of the blue. Their support team claimed the decision was final under their Terms and Conditions and refused to provide any specific evidence or discuss the matter further. This is a system with zero transparency, allowing them to ban anyone without justification. It's unprofessional and authoritarian. I'm convinced the ban was retaliation. The day before, I politely asked a team leader for feedback on why my bug reproductions were rejected, since they had been rejected without any reason provided. I was simply trying to improve. The next day, I was banned. When I asked for clarification about what I did wrong, support refused to specify which actions resulted in the ban. This isn't an isolated incident. Outside of their carefully managed communities, others have shared identical stories of being banned after disagreeing with staff. It’s clear that Test IO treats its testers as completely disposable. A warning to anyone considering this platform: think twice. Test IO's lack of transparency and respect is a major red flag. They can ban you for any reason, or no reason at all, and you will have no recourse. To Test IO: Should you reply to this review, I invite you to provide a specific, honest reason for the ban. A generic response citing your T&Cs will only validate the concerns raised here about unfairness and lack of transparency. To be credible, your response must include the specific reason for the ban. If you can't, you're just proving my point that you banned me unfairly.

This platform is too strict and the support people are not friendly, they always seem to be condescending and always think they are right. On the other hand they do not give new testers a chance to develop. The rules they make are all for their own benefit and not for the tester community that is working.

I was in the process of signing up with Cirro/Test IO but stopped as soon as I read through their Terms and Conditions. The legal risks for freelancers are shockingly one-sided and not what I’d consider fair or reasonable. Two clauses in particular stood out: • Indemnity: If anything goes wrong, the freelancer is responsible for any losses, damages or legal costs, with no liability cap. That means potentially unlimited personal exposure. • Confidentiality penalty: They reserve the right to fine freelancers $1,000 per breach, even without proving actual damage. One accidental slip could cost a lot. Other concerning points include: • Mandatory U.S. arbitration in Pennsylvania, which makes it impractical for non-U.S. freelancers to contest anything. • Full waiver of all intellectual property and moral rights. This means anything you produce while working for them legally belongs to them. You can’t reuse your own test cases, bug reports or scripts, and in some situations you may not even be able to describe the specifics of your work on your CV. For example, you could say you worked as a tester for Test IO, but not “I wrote regression scripts for X” or “I designed test plans for Y” because those outputs are legally theirs. • The company can change the terms at any time without your agreement. This might be acceptable for someone doing small side gigs and willing to accept high legal risk, but for most freelancers these terms offer zero protection and maximum liability. I strongly recommend reading the full Terms and Conditions before signing up. I decided not to proceed.

A company that has its employees at heart. You'll think being a crowd-testing platform would mean that they will be nonchalant in helping,assisting and guiding its testers that are falling short of their standards but that isn't the case. They continue to provide support and tips to help you become a better tester.

I was looking for different options for additional earnings online. I read a lot of reviews, watched videos, and chose this platform. I went through onboarding without any problems, the community helped me at every step. And now I have already received my first payment! I recommend it!

Be very careful with this company. On paper, they have a course that "anyone can take to become a tester," but in practice, the course becomes incredibly difficult, and the requirements for completion are absurd (especially in the final modules). There's no training, and there's no financial compensation for taking the course. Furthermore, the support team fiercely defends its business model, claiming it's voluntary and doesn't accept feedback. A total disaster.

Test IO is a great platform for testers at all levels. It's fair in its operations, offers a steady stream of opportunities, and the community is welcoming. The team leaders are supportive, responsive, and always willing to help. A solid choice for anyone looking to grow in the testing field.

Starting as a freelance tester, I gradually built up the experience and skills to become a team leader. Since then, I've taken a variety of roles across different teams in the company. I couldn't feel prouder or more grateful to be continuing my digital nomad lifestyle, all while learning more about the ever-fascinating IT industry. Test IO is indeed the place to make it into this industry, make a living out of it, and learn in the process, all together!

TestIO is reputable crowdtesting platform that offers flexible earning opportunities and diversified testing experience, however earnings depend on competition and quatity of bugs found.

After 6 months with Test IO, I'm satisfied with this platform. I think the platform should improve how testers can check known bugs. Unlike team leaders, we cannot easily verify whether old bugs have been archived, which makes it difficult to avoid reporting the same bug again. Additionally, team leaders should use their judgment to distinguish between those who intentionally copy and those who accidentally report bugs that happen to be similar to archived ones. Unfortunately, I encountered a team leader who insisted on marking me as a copier with a bug that same a archived one, even though I had reported several new bugs in the cycle —many of which he forwarded to the customer. Because of this experience, I’ve decided not to work with him again. And now I understand why many top testers choose not to join his test cycles.

I literally think they abuse the tester, less than 30% accepted bugs, for payment, but later on they were fixed. Projects with 400 known bugs, and they expect to have you first search all those and then test. Here's a tip, fix those bugs! And then retest! Nobody is willing to test an app with hundreds of bugs and to exclude the duplicate, just to hope maybe will find something new, and earn 2-5$. This is insane! I have analyzed other tests, 90% testers are new joiners. 70% of tests are rejected. I bet they reject them, and then a friend or family members will make money by resending that bug that will arrive at the client. Later added / reply: Of course we know that known bugs are controlled by the client, but they are YOUR clients and you have a say in this. Training has nothing to do with this, unless you are trying to say "we train you for free so work for free". Testers rejected is one thing, number of bugs rejected is another thing. Exactly my point, you reject bugs not testers. I truly hope you realize that. If you say you are fair with the testers think about the fact that they open a website with 400 known bugs, and spend hours to find bug only to see that the bugs they found were reported weeks ago, not fixed and they wasted time. Or if they find one or two bugs they are paid 2-8$ for a bug and they spent hours to filter the known bugs, which is a very low compensation

This app literally saved my life this is the best app ever created

Test IO is a crowdsourcing testing environment, It's a great website if you want to hone your skills as a manual tester. You can earn a little money as a side hustle job. The community of Test IO is wonderful; Testers from all around the world who will compete with you, help you and even give you advice to improve your testing skills. Don't expect too much from making huge coins from Test IO; consider this a training session for your QA tester career.

Test IO is a best freelancing platform you can make money by just testing..I recommend to you

Tester IO is great because: - Payments are really good - There are many opportunities for new and old testers - Many tournament such as Testing Cup; Newbies Testing Tournament - A ranking system with badges, points and additional prizes

The best QA testing I came across. Testio is where there is plenty of opportunity. If you want to earn and still learn then 💯 testio is for you.

Me encanta hacer esto con test io

The best platform to work freelance and get to test the latest web products. Everything is so simple and yet so effective. I encourage people to join this platform. I also encourage web businesses to consult testio and get your product tested thoroughly with high quality outputs.

It is a Great platform for a person like me who wants to earn from home. Although in the beginning one might feel discouraged but with time it'll get better and better. They have an Academy and discord channel where we can learn a lot!

Test IO is one of the best platforms I’ve ever used. I’ve learned a lot from it, and it has significantly helped me in my real-time QA roles—especially in writing well-formatted and structured reports. The Team Leads (TLs) are generally very helpful and supportive, and the platform also offers interactive learning sessions on their Discord server. These sessions are not only interesting but also practical and beneficial for real-world testing scenarios. Additionally, the community is responsive on Discord whenever you have doubts or queries, which adds great value. That said, I do have a few suggestions for improvement: 1. Warning Policy: The current "three warnings" policy feels a bit strict, especially considering it applies over a tester’s lifetime on the platform. I believe that after a certain period, these warnings should be reset if the tester has shown consistent improvement. People grow and learn, and offering them a clean slate after demonstrating progress would be motivating and fair. Of course, if mistakes continue without signs of improvement, stricter action would be understandable. 2. TL Reporting Process: Some TLs (not all) tend to report testers immediately without giving a prior warning or guidance. I don’t think this approach is entirely fair. Everyone can make mistakes occasionally, even TLs. For example, if a tester received a warning in the past but makes another mistake after a long period, the TL should ideally inform them first rather than immediately reporting it. This kind of feedback loop would help testers improve and would benefit the overall quality of the platform.