test IO Arvostelua 198

Công ty band nich mà không có một thông báo nào, Coi thường người hợp tác cùng .

The biggest issue I’ve experienced on Test IO is the inconsistency of the review process. Many times it feels like the outcome depends entirely on the reviewer’s mood at that moment. A valid bug can be rejected simply because the reviewer interprets it differently that day, and the same report might be accepted by another reviewer under identical conditions.

It’s also extremely difficult to understand what is considered a real bug versus “intentional behavior”, because the criteria are not applied consistently. Even when multiple testers reproduce the same issue and confirm the behavior, the report can still be rejected without a clear explanation.

Additionally, the Team Lead often does not respond to clarification questions, which makes the process even more unclear. Valid bugs are rejected without proper justification, and in several cases issues are incorrectly marked as “duplicate” or “out of scope” even when they clearly belong to a different pipeline or scenario.

In many situations, other testers have confirmed the exact same problem, yet the Team Lead still rejects the report. This creates the impression that the review decisions are not based on the actual behavior shown in the video, but on subjective interpretation.

I personally had several clearly reproducible and relevant bugs rejected, even though the video showed the exact behavior step‑by‑step. In multiple cases, the rejection reasons (such as “duplicate” or “out of scope”) did not match the actual scenario or the pipeline involved.

This creates a significant risk for testers: you can invest a lot of time and effort into finding and documenting important issues for the customer, but there is no guarantee of earning anything. Important bugs that matter to the customer can be rejected without valid reasoning, leaving testers without compensation despite meaningful contributions.

This level of subjectivity makes the process unpredictable and discouraging. More stable standards, clearer definitions, responsive communication, and consistent application of the rules would greatly improve fairness and trust in the platform.

Went through the entire "onboarding" process for 2 hours, only to get banned at the end for "suspicious" behavior, with no further explenation.
Don't waste your time.

Positiv: Wurde zuverlässig über Paypal ausgezahlt, professionelles Feedback zu den eigenen Bug Reports, Einweisung macht Bug Reports schnell verständlich, viele Testeinladungen, kann Spaß machen, anfangs sind die Tests einfach und es kostet nicht allzu viel Zeit Fehler zu finden

Negativ: Hohe Anforderungen, öfter werden Reports abgelehnt, zb einmal nur weil Screencast ein bisschen zu lang war, Bezahlung zwar nicht katastrophal aber doch unter Mindestlohn, Mit der Zeit werden Tests deutlich anspruchsvoller und spezifischer, es wird schwieriger Fehler zu finden und kostet mehr Zeit, vielleicht kommt man da auch wieder rein wenn man es öfters macht

After hours of study, took the functionality bug test once which says I have 5 chances. AI said it was good and may qualify so I submitted to TL. TL wrote a lot and asked me to try again but I couldn’t find the option to try again. I contacted support and was told I have no more chances and will not be moving forward and that was it. One test and all my time and effort wasted! If this is across board not targeted how many people make it in one try? Painful experience!

It has been 3 months since I joined Test IO, as a side hustle and I can attest it has been amazing so far.
It helps if you have been into Quality Assurance for a good number of years yourself. :)
The onboarding modules are strict and for a good reason. There are few improvement (noteworthy) points (regarding onboarding) for sure, such as system flagging the reports as AI written even when they were 100% written by a human (viz. me).
It's all about patient and the zeal for learning. Looking forward to contribute more in coming days and months.

**“The platform was extremely strict. I kept getting rejections for almost every bug I reported, even though I was mainly trying to learn as a new tester. Invitations to participate in tests usually arrived very late, and most of the time there were no available spots. When I did manage to report bugs, they were often marked as duplicates because someone else had already had enough time to report them before me.
Not even two months passed before I was excluded due to a low bug acceptance rate, even though I had been promised two additional weeks to improve since I was a new tester. In the end, I had accumulated a small amount of money, but they didn’t pay it out even though it had passed the threshold.
Whenever I tried to contact a team leader or support, I only received automatic, robotic responses. It was the worst experience. I lost two months of my time and felt very bad and extremely disappointed.”**

I’ve had a very positive experience with Test IO so far. The learning resources in the Academy are top-notch, and the platform is a great place to build professional testing skills. While the competition is high, the support and Team Leaders are generally very helpful. I'm excited to contribute more and grow my career and income with this community.

It's been almost 5 months that I joined the testio community and all I can is that I'm loving it. The only issue I'm currently having is not that I have not been able to collect my earnings due the platform rejecting my TIN which was provided to me by my country Nigeria. Please this issue is not encouraging me at all. While I am still enthusiastic about being a member of this community if this issue continues I might have to leave which would be so sad for me.

I have had a very positive experience testing with Test IO. Whether you are completely new to crowdtesting or an experienced professional, it is easy to blend in and get started. The platform rewards dedication—if you take the work seriously, you will do very well here. Additionally, the support team is excellent; they are highly responsive, friendly, and genuinely helpful.

The only reason I am giving 4 stars instead of 5 is because of the mobile app and mobile web versions. I occasionally encounter bugs and inconsistencies when comparing the mobile experience to the much smoother desktop version. However, I always report these bugs to the support team, and they are great about forwarding my feedback directly to the developers.

Overall, it is a fantastic platform with a great community, and I highly recommend it to anyone serious about testing.

I have Learnt a lot from joining the "newbie-testing-tournament-01-2026". Now I can write a bug report in a good way, add attachments with clear evidence. Thanks TestIO team.

I've gained alot of experience on Test.io platform not just earning alone but learning and this boost my sense of reasoning to just get better in everything. Working with the TL's instructions is a great and having a good interaction with experience testers has done me alot, most especially during the Newbie testing tournament, this helps alot.
Thanks

I really liked how clearly and correctly the teamwork was organised. Help and advice were available at every stage.

Test IO is the best. Thank you for all the opportunities you have provided.

I really like the way testIO always ensures that testers get all they need to excel in the platform. The message is clear: "Get used to finding bugs in a competitive environment and document those bug report like a pro". I'm glad I participated in the newbies tournament. It was fun...

Clear Instructions.
Helpful Tutorial Documents.
Helpful Youtube Channel.
Helpful Discord Channel

I failed the onboarding test four times, not because I didn’t try, but because this process is absurdly rigid and completely disconnected from real learning. You can follow every rule, read every guideline, and apply every piece of feedback, and it still won’t be enough.

This isn’t onboarding - it’s gatekeeping. The feedback is nitpicky, repetitive, and focused on semantics rather than actual problem-solving. Instead of helping you improve, it drains your time and motivation.

If you have literally anything better to do with your life, do that instead. This experience was a complete waste of time.

I have been working as a freelance software tester for 5 months, the website navigation is very user-friendly, onboarding tasks required to start working are clear and depends on the courses provided by the website, If you have questions you can ask support and they reply fast, sometimes within 1 hour, also there is a discord server where you can ask testers like you,
Every test cycle you join contains instructions that if you feel something in it is ambiguous you can ask the team leader in the chat about it, If a bug you submitted got rejected, the team leader give you a clear reason of rejection and you can actually discuss him/her about the rejection or open a dispute if you believe it shouldn’t be rejected,
For me i have been enjoying my time working as a freelancer on Test io and I believe it is a great way to practice finding bugs and enhance your skills in SQA, I believe that anyone can earn a lot here when working hard, Because Bug hunting is a skill that requires practice and as long you are improving in it you will earn more.

My experience testing this app raised serious concerns about the risk–reward balance imposed on users and testers.

The onboarding and core flows rely heavily on ambiguous or misleading behaviour that shifts risk to the user without providing corresponding value or transparency. Key examples include:

Testing the functionality of broken ambigiously worded apps that are later not accepted as buggy but are intended to work in this way.

Testing apps that simulate security or system-level behaviour (for example, appearing to lock the screen) without actually enforcing that state and stating the app is "intended" to work that way.

Testing apps which make requests for elevated privileges (such as call-related or system access permissions) without a clear explanation of necessity or demonstrable benefit to the user. Increased permissions increase exposure and risk, yet no proportional reward is evident.

Distribution via sideloaded APK rather than a standard app store channel, which places additional security and integrity risk on the user while offering no compensating safeguards.

Individually, these choices may be defensible as “intentional design.” Collectively, they represent a pattern of risk externalisation: the user is asked to accept higher levels of exposure, ambiguity, and trust, while receiving minimal clarity, control, or value in return.

For users who are security-aware or risk-conscious, this imbalance is difficult to justify. Trust in platforms and application are built through transparency, proportionality and respect for user boundaries. In this case, those elements are weak or absent.

I would advise potential users and testers to carefully consider whether the risks being asked of them on this platform are matched by genuine utility or benefit, and to proceed cautiously if they value clear security guarantees and honest system behaviour.

21/1/25 Update in response to test.io reply addressing their definition of "misinformation" and to reiterate the salient points of my initial review.

I would like to clarify that my comments were not intended to narrowly define onboarding as the initial qualification tasks alone but rather to describe the early-stage tester experience as it is encountered in practice, including the transition from qualification into initial test cycles.

While I acknowledge that the formal onboarding process focuses on understanding instructions, creating attachments and submitting reports, the concerns raised in my review relate to what testers are exposed to immediately upon joining test cycles, particularly early assignments where context, intent and risk are not clearly communicated.

Specifically, my observations relate to:

Applications presented for testing where ambiguous or misleading behaviour is later classified as “intended design,” despite that intention not being clearly conveyed within the app or accompanying test instructions.

Scenarios where applications simulate system-level or security-related behaviour without enforcing it, creating ambiguity for testers tasked with assessing functional correctness or security-related flows.

Requests for elevated permissions or sideloaded APK installation during test cycles, where the necessity, safeguards, or proportional benefit to the tester are not always clearly articulated.

These points are not a claim that such practices occur during the qualification tasks themselves but rather that they form part of the practical risk profile imposed on testers once they begin participating in live cycles in the early stages of their engagement with the platform.

My use of the term onboarding was therefore descriptive of the initial tester journey, not a technical assertion about internal process boundaries.

I recognise that your Terms and Privacy documentation exists and that safety is stated as a priority. My concern, however, is about how risk, ambiguity and responsibility are experienced in practice by testers—particularly those who are security-aware and whether those risks are proportionately matched by transparency, clarity and reward.

I appreciate the opportunity to clarify this distinction.

Good for those starting their careers in testing and i loved the onboarding.My account was banned anyways because i violated one of their rules.In their T& C it is indicated that testers who are banned are paid all the money they're owed.This hasn't happed yet to me.I am told the money will remain in Cirro since it hasn't reached the minimum threshold for withdrawal. This is ridiculous since there's not possible way that it will reach the threshold since my account is banned and therefore i cannot work to the threshold.Rules should apply to both parties