Tester Feedback

Icons of testers without added profile pictures, and icons of team leaders are the same. For example, when you read a chat, it would be convenient to find the messages of the team leader in the chat, by the original avatar icon, which belongs only to the team leaders.

The same ways things were last year are not how things will be this year. We should be getting significant increase in payout per bug across board this year so as to motivate us more as a tester.

Hello, From my perspective, The idea of requesting a payment and waiting 10+ more days for it to be processed is a little bit discouraging. I hope this is comfortable for the platform

Each team leader has his own criteria for making bugs. The same bugs different TL reject for opposite reasons. Already, many times the bugs that some TL forwaded and the customer accepted were rejected by other TL. One TL considers the error visual, the other considers the error as functional. TestIO academy rarely help reach agreement.

I have many times encountered that customer have rejected bugs as intentional behavior without giving any further reason to it. This makes it very unfair to the tester, who has no option but to dispute just to get more clarification on it. As such the description or reason field should be mandatory and even have a minimum character limit so customers give proper reason as to why they have rejected the bug. After viewing the reason, tester can decide if he has to dispute or not.

The overview before test is not sufficient or updated in most of the cases which cause confusion and rejection of bug. If the chat could be accessed before accepting a test cycle, testers could clarify the doubts and decide to accept invitation or not.

Let's think a bug is either rejected by TL or customer which already includes 3 reproductions. All reproductions are valid. But since original bug is rejected, no bonus is paid for both original bug owner or reproducers. But original bug owner opens a dispute and it is successful. Then, dispute bonus is paid only for original bug owner. Reproducers are not paid even if their reproductions are valid. I believe this should be changed because reproducers too made a valid contribution and they have spent some time to reproduce bugs. If bug is mistakenly rejected either TL or customer but accept after successful dispute, I think reproducers also should get the benefit of payment. This is my idea.

I suggest for a great testers to make a reward system. Now the great tester has only one advantage: it is an opportunity to choose any of his devices for testing, if three great testers are not already registered in the cycle. You can take advantage of this advantage quite rarely. I propose to make a reward for great testers for the quality of reports. For example, if the quality of reports is more 80% then add to the total amount some amount per month. Ideal if there are four stages: > 80, > 85, > 90, > 95. This is more motivating testers to do quality reports.

In some scenarios, user cannot install apps or unable to perform testing. User should be provided a text box to mention the reason along with options displayed. This helps leads and managers to know what exactly the reason for tester to quit. example: User may not be able to install apps due to some tech issues and he selects "technical issues" option but leads and TL' may not know what is causing the issue. Some times on clicking installation url, blank page is displayed so this can be mentioned in text box