Nov 2
New principle of distributing testers in repeated cycles!
Today, when a re-cycle comes, testers who participated in the cycle before and added the necessary bugs can re-report their bugs in re-cycles.
**We see that the same tester from cycle to cycle adds 10 bugs in a row for the first 15 minutes of the cycle.**
This is an incredible behavior when viewed from the perspective of competition among testers!
What contributes to this?
- Due to the fact that the customer's name is not hidden and the cycle description is open, this allows the tester to prepare and copy the required description. The required screencasts are recorded by this tester when the cycle started.
- This behavior has all the signs of preliminary testing.
Yes, you will say that it is not forbidden to submit repeated bugs.
But.
***When one tester prepares to recycle and adds 10 bugs in the first 15 minutes, which is 40% of the total bugs, this creates a negative impact on other testers.***
Why?
***- The principle of competition among testers has been violated!;***
***- There are all signs of preliminary testing!;***
***- Thus, the platform creates opportunities for only one tester in repeated cycles, which is simply incredible!;***
***- Only one tester gets paid in repeated cycles!;***
**I propose a new principle for distributing testers in repeated cycles.**
- If tester "@" participated in the first cycle, then this tester "@" will not take part in the second cycle, because this tester "@" will prepare for the second cycle, **and will add 10 bugs in the row in the first 15 minutes.** Accordingly, the tester "@" who missed the second recycle will be invited to the third recycle, and this tester "@" will fight other testers about repeated bugs!;
- Or invite this tester to repeat the cycle only once a month;
**Thus, repeating cycles will not be a reason to run only one tester!**
Closed