Bug review should mandatorily begin in the last hour of the test cycle if 20% of submitted bugs haven't been reviewed
S
Shalom Karunwi
This is particularly for test cycles which haven't had a single bug reviewed at the expiration of the allotted time.
There are cases where testers are unsure if a bug is a duplicate and wait for the TL to review the similar bug, but the TL doesn't begin review until the test cycle ends.
This also helps for bug reproductions where there isn't sufficient clarity as to whether it is a bug or not.
AV-Master
Hi Shalom Karunwi. Thank you for your feedback.
Team leaders are freelancers just like testers. They check at a time that is most convenient for them. They usually have several cycles and therefore checking test cycles can take an indefinite amount of time.
In this case, you should rely on your experience as a tester and identify duplicate bugs yourself. The same goes for reproductions. I understand your desire to make only reproductions of those bugs that will be forwarded in order to receive a guaranteed reward for your work. But in the case of a highly competitive environment, you may not earn anything, because there are testers who make all the reproductions without understanding whether it is a bug or not. Thus, they have a high rate of reproductions of bugs that will be rejected, but they are guaranteed to earn more than testers who wait for bug forwards to make a 100% paid reproduction.
Understand also the desire of team leaders to begin and fully check the test cycle once and never return to it.Therefore, it is very convenient for them to perform the final test cycle check when there are definitely no additional bugs, userstories or reproductions that need to be checked.
Therefore, it seems to me that this can be regarded as a recommendation for team leaders, but it will most likely be difficult to make this a rule.