There should be given time left for bug reproduction only in a test cycle
Drake mick
In most cases I see that in test cycle some bugs been forwarded to customers without any reproduction. In such case it may be the time such tester submitted the bug.
I would suggest there should be more time left for tester to reproduce forwarded bugs even when time given in a test cycle as ended. bcuz we still have some tester that can earn little from bug reproduction and get smiled... Thanks
Tetiana Yezerska
AV-Master
Another problem is that the tester starts to reproduce, but does not have time to add a screencast, since the cycle time is running out.
A bug with the lack of simultaneous reservation of reproductions by several testers has been reported and will probably be fixed soon.
ted
There is no point in this request.
The team leader followed the steps and discovered that the bug was reproducible.
Afgan Sofyan
ted: That's just the first request in this thread.
Also, there's a point in giving the customer a reproduction because they pay for it (assuming the TL doesn't submit it).
Afgan Sofyan
I agree. There's a case when a reproduction slot for certain bug reappears, maybe because there's a submitted reproduction that's rejected, but unfortunately the time cycle just last about 2 minutes. Even though the reproduction time keep running, your submission will be forbidden when the actual time of cycle already over.
Tetiana Yezerska
Merged in a post:
Allow simultaneous 30-minute slot reservation until fulfilling all the reproduction slots for a bug
Kailash Joshi
Instead of having a single tester reserve a 30-minute slot for bug reproduction, which causes other testers to wait for a slot to become available, it would be more efficient to allow all testers to reserve remaining slots for that bug. This way, all the slots for reproducing a bug can be filled in a shorter amount of time.
The benefits of this approach are:
- Testers can complete their work more quickly and move on to other tasks, without having to wait or anticipate.
- More bug reproductions can be done, as opposed to the current scenario where slots can go unused.
- Later bugs logged in the test cycle will have a better chance of having more reproductions slots covered, since multiple testers can reserve slots within the 30-minute time frame.
ted
The best solution is to simply remove reproductions forever, firstly, testers always send negative reproductions, even realizing that the bug itself is reproduced, this is done to spite the tester. And the second point is saving money for the platform.