课程: Software Testing Foundations: Bug Writing and Management

今天就学习课程吧!

今天就开通帐号,24,700 门业界名师课程任您挑!

Closing bugs

Closing bugs

- [Instructor] When people think about closing bugs, there is an assumption that closed means fixed. In reality, closed simply is a status. When a bug is open, development remains committed to dealing with the issue. When you close a bug, you aren't applying any particular value to it. You are simply saying that nobody is working on the issue any longer. This distinction is very important because there are a lot of reasons bugs close. First, the obvious and best reason to close a bug is because it's been fixed. If you have thoroughly tested the issue and your bug is corrected, you will change that status to close so you can focus on other issues. You'll add notes about how or what was fixed and document the testing performed to verify that it was indeed corrected. Bugs can also be closed because the developer hasn't been able to reproduce the issue. It's not uncommon for anomalous bugs to appear during testing…

内容