From the course: Tech on the Go: Building a Software Test Department

Unlock this course with a free trial

Join today to access over 26,500 courses taught by industry experts.

Effective bug reporting

Effective bug reporting

From the course: Tech on the Go: Building a Software Test Department

Start my 1-month free trial Buy for my team

Effective bug reporting

“

- [Instructor] Effective bug reporting. Throughout the course of testing you'll find problems to be solved. These bugs and defects should be documented and sent to software engineers to be fixed. Software engineers have their own set of tasks and expectations that they're constantly balancing and their time and bandwidth are finite. A poorly written bug report can distract and waste time with clarifications and unnecessary investigations. There may not be a direct line of communication between the person reporting the issue and the software engineer. What's the best way to communicate the issue? In a structured document known as a bug report. A well-structured and appropriately detailed bug report should clearly guide software engineers to what needs to be fixed in the least amount of time. An effective bug report should be able to clearly describe the concern to any reader and answer a few key questions. Bug reports…

Contents