From the course: Software Testing Foundations: Bug Writing and Management

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Closing bugs

Closing bugs - Jira Tutorial

From the course: Software Testing Foundations: Bug Writing and Management

Start my 1-month free trial

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…

Contents