From the course: Software Testing Foundations: Test Management

Unlock the full course today

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

Bug tracking

Bug tracking

From the course: Software Testing Foundations: Test Management

Start my 1-month free trial

Bug tracking

- [Instructor] We have already briefly examined the best practices associated with logging issues discovered during testing. Recording the problems discovered is a big part of the quality team's duties, but what is equally important is maintaining issues after they've been logged. The exercise of monitoring the issue after it's entered is called bug tracking, and it's a big part of the lifecycle of a bug. Bugs don't disappear after being entered into the tracking system. Once an issue is recorded, it's a little bit like a package being shipped. You are placing all the important details about your discovery into a container and it's passed around until someone takes ownership, addresses it, and either returns it to you for regression testing or closes it. Your submission doesn't end when you share it. In our Explore California project, the team's issue with reservations doesn't fall on the shoulders of development…

Contents