Tester Feedback

Even after the recent changes made that all tests before 10th will be paid in a week's time, there are many tests which are not closed even though all bugs are reviewed and it's only done after 10th only to be paid in the next cycle more than 30 days later. The time taken when the test is completed and the payout received sometime exceeds 50 days. I propose two options two tackle this issue Work with customers to close a TC where all bugs are reviewed within a week. Introduce Biweekly payouts so we don't have to wait longer for tests which are not closed by 10th

Now, whenever a tester opens a test invite to accept it from Test IO website, they have to scroll all the way to the bottom of the page. I don’t see any real benefit of moving the accept invite section to the bottom (maybe I am wrong), but as a tester, I am definitely facing some disadvantages because of it. You have to scroll down to the bottom, especially on mobile view, where it becomes a bit of a time consuming process. This is very disadvantageous for testers like me who want to check if the system has opened the desktop device as the selected one in the device selection dropdown, especially when the requested device is mobile but desktop is also available. The only way to check this is to refresh the page repeatedly, but after every refresh, the tester has to scroll to the bottom again, which makes the process even more time-consuming. I believe that due to the high saturation of testers in Test IO, the time to accept tests has already reduced, and placing the accept invite section at the bottom has made the test acceptance process even more lengthy and frustrating. So, in my opinion, the old design was more user-friendly.

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.

Problem Testers must open each test opportunity individually to check suitability, creating inefficiency in test selection and sometimes accepting tests where they would most likely not provide much work. Solution Our AI could add Match Scores or Suitability Labels directly on the dashboard for each test opportunity. Visual Indicators • Match Score: Percentage (85% Match) or star rating (⭐⭐⭐⭐⭐) • Colour Labels: 🟢 Perfect Match | 🟡 Good Match | 🔴 Poor Match AI Scoring Criteria – Level Benefits: Matches tests to Copper→Diamond level privileges – Profile Factors: Device compatibility, performance history, availability – Specialisations: Skill tags, geographic requirements Key Benefits • See test suitability at a glance • Focus on most appropriate opportunities • Reduce dashboard navigation time • Improve test selection success rate Implementation Display match score next to test titles Add tooltip explanations ("Great match: Aligns with your Silver benefits") Enable filtering by match score

While it’s true that most testers participate to earn payouts, it’s not always about the payout alone. Sometimes bugs are technically valid but don’t meet the required severity for payment. These bugs should still be acknowledged—not necessarily with payout, but at least through backend review or developer insights. Having a neutral way to record such valid but non-payout bugs would help avoid discouraging testers and ensure potentially useful findings are not lost. This approach would also prevent unnecessary negative impact on BRAP scores caused by rejecting technically valid reports. Suggestion: Implement a system to track and acknowledge valid bugs that do not meet payout severity thresholds. This could include a “neutral” status or tag that does not affect BRAP scores negatively but flags reports for backend or developer review. This would encourage testers to submit useful bugs without fear of penalty and improve overall report quality.

While the chat option is available in every test cycle to clarify doubts, severity-related expectations are sometimes not explicitly discussed or confirmed in time—especially in fast-paced cycles. This can lead to valid bugs being rejected simply because they are not deemed critical enough. To improve this process, I suggest: Clearly communicating severity expectations within the test scope, ideally with examples for clarity. Allowing bug submissions to include an optional note such as “Valid but not critical” for team leader or developer consideration. Implementing a “soft submit” or “review-only” tag for educational or informative bugs that may not qualify for payout but provide valuable insights. This would help testers better understand expectations, reduce frustration over rejections, and support a learning environment.

During a recent test cycle requiring Safari on macOS 14 and higher configurations, Safari failed silently, likely due to macOS privacy restrictions. There was no option to change the environment; Safari was pre-selected. I initially recorded the bug using Chrome and marked Safari as the environment, fearing my bug would be rejected if I delayed further. Later, with help from the Test IO Discord server, I discovered a working workaround using the PreProxy app, even though existing documentation is outdated. With PreProxy configured, I was finally able to run the test on Safari successfully — no prompts, no issues. 🔗 Reference: Discord Fix Discussion: https://discord.com/channels/562544573952294912/624515360170835988/879362209489223721 Suggestion: Please consider: Adding an article or Academy lesson covering proxy setup for macOS Safari, especially using PreProxy. Mentioning known limitations with Safari and proxy. Clarifying how testers can proceed when no prompt or fallback is available. This would prevent confusion during time-sensitive cycles and support testers working with Safari environments. Note: This is a known issue and not a bug report. Just feedback based on real experience. I’m not implying this is mandatory — just sharing for consideration.

After earning a badge, when clicking on the notification in the mobile app, I am not redirected to the badge section. Instead, I have to manually navigate there, which affects the smoothness of the user experience. This issue does not occur on the web app—there, clicking the badge notification correctly takes me to the badge page. Suggestion: It would improve user experience and consistency if the mobile app notifications redirected users directly to their badge page, just like the web app does. Note: I cannot provide a screenshot or screencast at the moment, as no new badge has been awarded recently. I will share attachments as soon as a new badge notification occurs. - Screencast has been uploaded

Every time a tester subscribes to a cycle, this email is sent. Honestly, this email is wildly tired. The interface clearly shows that the tester is subscribed to the cycle. Remove this email because it just bothers or make a setting so that can turn it off. This is one of the dumbest emails around.

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.