Mar 12
The team leader is not allowed to check bugs when more than 2-24 hours have passed since the close of the cycle!
There are cycles where the time is set as 2 days.
Testers added a lot of bugs and did a good job, but, unfortunately, this is not enough, because the cycle itself is closed and there are a number of reasons:
1. The team leader very quickly wants to do his job to quickly close the cycle itself and not return to the cycle anymore. Because of this speed, the team leader is inattentive, and testers suffer for this.
2. The team leader does not always try to reproduce the bug itself, and does not think about the bug itself 100%, so the tester remains with nothing.
3. The team leader does not have the device on which the tester added the bug itself. The team leader rejects the actual bug as it is impossible to reproduce, although the bug itself is reproduced and the tester should have received a request and add proof!
Bugs should be checked during the cycle always and not later and later.
The team leader must understand that he works with people, that people spent their time to do the work and not just get a rejection.
It is not always possible to send a dispute, because attempts are not enough, and the tester himself is left with nothing for the second time.
It’s very difficult to win a dispute where the team leader wrote an incredible reason for rejection..
Closed