Improvement regarding Warning Policy and TLs reporting process
under review
Mozaffar
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.
Tetiana Yezerska
under review
Mahmood
Thanks, number 1. is a great advice! Personally, I got a warning in the very first test that I participated in, because I submitted a reproduction to a bug (which sent a msg to an actual user to test messaging functionality). As a greenhorn tester, I had no idea about any rules of the platform. It was only after I was given a warning, I was contacted by support and was told to read an Article (wish Test IO made it mandatory to read that article, for greenhorn testers, before participating in their first cycle).
Now, this mistake is going to cost me for the rest of my days as a tester on Test IO. So, if these warnings get reset after a time period(let's say a year), this would be highly motivating for a tester.