Tester Feedback

It happens often that a tester can miss a test inviation and when the tester sees the notification there are no more slots in this test and it dissapears from the dashboard.Anyways after a while a slot can be avaliable and the test inviation appears in dashboard. I suggest that a notification will be sent (by email and Testnow app) to the testers who missed the invitation when a slot becomes avaliable and the invitation is shown in dashboard, in order to accept the test invitation immediately.

Please show user story which is available without stating session

After half of the test cycles, testers have the opportunity to use all their devices to execute user stories and submit bugs. Unfortunately, the devices are not organized by type and it is inconvenient to search for the desired device to select. I suggest ordering devices by type and by OS. For example, desktops Windows | macOS | Linux) are shown first, then tablets (Android | iOS), smartphones (Android | iOS), and other devices. If in the case of executing user stories or submitting bug reports this is relevant after half the cycles, then for reproductions this is relevant all the time.

Tester should be allowed to delete user story (pr ability to modify) //If required you can keep some tiemframe. say , user can edit it withing 1 hour of submission or something like that

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.

The minimum payment for reproductions should be € 1.

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)

Currently, on the tester profile, the bug approval rate is getting updated after submitting a bug report, even before the TL reviews the bug report. If a tester submits 10 bugs in a cycle, the bug approval rate will get reduced. If the tester level downgrade from diamond to the lower level,and if a new cycle launches at that time, then the bonus payout will not be calculated. I suggest to update the bug approval rate in tester profile only when the TL reviews it.

Right now, we can not know that the TC requires proxy/VPN before we accept and Test Cycle starts. I sometimes can not reach any wifi and have to test with cellular data. Because I do not know the requirement before accepting the TC, I can not be beneficial in such Test Cycles. I have to wait till reaching a Wi-fi. This situation is "similar for VPN" also. Testers may prefer test cycles without VPN because of technical difficulties or personal prefers. It is better to provide the requirement about Proxy and VPN before accepting the TC (maybe with the email invitation) so that the testers know these requirements before accepting them.

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.