Tester Feedback

Its four months into the post-Cirro era and personally, payments are now slower than ever. More often than not, freelancers get paid bi-weekly, and if payments are going to be monthly the expectation is that they come in swiftly to accommodate the wait-time. Last year it was a lot faster than it is now. Here's what I propose: The payments request window should last a maximum of 3 days (10 days to initiate a payment request is quite unnecessary). Payments should be sent on the 15th of every month and the wait period to receive payment should be from the 15th - 23rd of the same month. Currently we work for 30 days and receive payments after another 21(+/- 9) days. This proposed timeline shaves off at least a week off of that without any dramatic disruptions to the current system.

Now devices usually are updated automatically, and in some test (e.g Streaming testing), when a tester joins a new cycle, then sees the OS of the device, it notices the device have updated to a new version, but the list of devices in the account section is not updated accordingly. The tester has to ask TL or contact support for this matter (request an update), but since tester needs to have the updated device OS to properly participate in test, the issue is sometimes TL doesn't want to update the list since it is not his/her function. It generates an issue to tester since he/she has to wait the response of customer support and therefore delays the time available for testing, and worst case, tester has to quit test.

Please show user story which is available without stating session

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)

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.

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 dispute are supposed to be the final stop at redeeming a bug decision, so it’s disheartening when the dispute manager doesn’t review the cycle (overview, instructions, bug lists and chat) so they understand the context of the test. On more than 1 occasion, I have encountered situations where the dispute manager’s response is out of context or irrelevant to the bug. So I would suggest we are able to respond to the dispute manager to review their decision A recent example involves a cycle where we were given a link to an html to be opened on browser and then sent the same html as email. The aim was to compare the 2 html and report any visual or content issue that differentiates the 2 htmls Also, in this cycle, each feature was a different client as clarified in the chat and from past experience with the cycle. So I submitted content bugs for missing phone number links which were present in the html on browser but TL rejected as functional. So another tester and I opened a dispute. In mine, I made the argument as to why it was content not functional, according to the academy and linked a video of comparing the html on browser with the email clients. The other tester also argued using academy, why it was a content and then linked the html browser link. My dispute was rejected as a UX and a duplicate, but the other tester’s own was accepted as a content bug. If my dispute manager had reviewed the cycle they would not reject for such reasons.

I want a message like: "Rejected - this is a duplicate to # 12345." I could click on part of the text # 12345 and the system will automatically open the page with error # 12345. Thus, I can immediately and easily open this error, and not search for it manually by the number