Quantcast
Channel: Should you close old bugs? - Software Quality Assurance & Testing Stack Exchange
Browsing all 11 articles
Browse latest View live

Answer by chrisc for Should you close old bugs?

Despite being an edge case, or low priority, if you can still reproduce the reported bug, and the expected functionality of that system still dictates that it is a bug (instead of just an old...

View Article



Answer by Joe Strazzere for Should you close old bugs?

If you find more bugs than you fix, then what should you do with the ever expanding bug queue? It has been proposed in my team, that we close bugs older than x days, as they will get re-submitted if...

View Article

Answer by bta for Should you close old bugs?

In my experience, closing a bug simply because it's old is not a good idea. My organization used to do this as a policy, but it caused a number of problems. The bug can look like it's fixed. Test teams...

View Article

Answer by user246 for Should you close old bugs?

There are two issues in the question: how you use your bug tracking system, and how your deal with having too many bugs. If you don't plan to fix a bug, you might as well make that apparent in your bug...

View Article

Answer by DWalker for Should you close old bugs?

When you close a bug, there should be a reason for closing the bug. The most obvious, of course, is fixed, but could not reproduce, not a bug and won't fix are equally valid. Could Not Reproduce means...

View Article


Answer by Niels van Reijmersdal for Should you close old bugs?

I think coming up with a good strategy of closing defects is very wise. I once worked in a team which had over 3000+ major, minor and trivial bugs of which most were at-least 2-3 years old in the...

View Article

Answer by Dakshinamurthy Karra for Should you close old bugs?

I would like to consider each of the cases separately: Low Priority - Low priority bugs do not stay low priority always. They always have a tendency to become high priority if enough of the users...

View Article

Answer by Edu for Should you close old bugs?

I would say that product owner (or whoever ultimately decides what the team works on) can decide that some bugs will not be fixed for one reason or another. Then I would close those bugs documenting...

View Article


Answer by Konsti for Should you close old bugs?

I would not close bugs - you can "park" them - but it shouldn't look like the bugs are resolved. In our software release cycle we have ~2 months bug fixing phase - in this phase most developers are...

View Article


Answer by Helping Hands for Should you close old bugs?

Bug is Bug , it does not matter how old it is. As a tester you should not close bug if it is not resolved yet by developer and verified by tester. Close old bug without solve and insert it again that...

View Article

Should you close old bugs?

If you find more bugs than you fix, then what should you do with the ever expanding bug queue? The queue can grow for several reasons: The bug is deemed too low priority to be worth fixing The bug is...

View Article
Browsing all 11 articles
Browse latest View live




Latest Images