Tester Feedback

I do have a few suggestions for improvement which will definitely helpful not only for tester but also for Test io growth: 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. 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.

Hello team, The Access claims page sometime become a blocker for testers when only limited claims are available and are already taken, testers wouldn't release them (specially when TL is offline so no announcements are available to be made) so only few testers are applicable to test. I hope you look into this problem. Thanks for your efforts so far.

Currently, I only receive a notification when the team leader mentions me in the test chat. However, if another tester @mentions me, I don't get notified and often miss the message. Please consider the following improvements: Send a notification when a tester @mentions another tester in the chat. Optional: In the settings, add a new option: "Chat @mentions by testers", so users can choose whether to receive these notifications or not. Rename the current setting "Chat @mentions" to "Chat @mentions by team leader" for clarity.

There are constant updates to articles in the academy, making it nearly impossible to track all changes. I suggest adding a changelog section that provides information on article updates or newly added content. This way, testers who are already familiar with the academy could quickly find out about updated or newly added information. The section should include: The title of the updated/added post A link to the post The date of the update This would allow testers to receive up-to-date information in a timely manner.

In test cycles there are sites that are tested repeatedly and the list of known bugs is very large. It takes a lot of time to get acquainted with them. It is simply impossible to remember, especially when you take part in several test cycles. The bug title does not always contain enough information to immediately understand it. You need to see the steps and screencast. It takes a lot of time. Sites with so many known errors should be paid higher. Now I take part in the test cycle # 40484 (319 known bugs)

Reproduction is the only reason if our bugs acceptable or not as an information to be forwarded to customer. But sometimes the bugs condition 'quite unique' and only ONE/Not-At-All positive reproduction that could be seen. Unfortunately, the testers couldn't really see them, and turned out: For negative reproduction: Some Testers want to confirm them via cycle chat, that's not simple (delay respond or not respond at all from respective testers). For positive reproduction: Testers could have a "blind trust" that mislead them to keep the bugs report, even when the reproduction is invalid. Thus, with all those concerns I suggest for testers to have a "right to see" reproductions of their own bugs, as information to decide validity of their findings. That's I believe will help to improve performance scores of the testers. Thank you.

When closing the tab or application on some sites, "Are you sure you want to close this tab without saving the written texts?" question should be added.

Hello. Can you please add a timeslot availability feature on test.io ? Sometimes I receive tests after it has already begun and then the space is filled up which is quite disheartening

Now it's onle no more than 15 seconds. But if you need to show order proccess it take more then 15 seconds. It also applies to other features.

The minimum payment for reproductions should be € 1.