Software Testing Glossary

Bug Owner (in BTS) is the one who is responsible for the bug. This person opens and closes the bug. This person also performs bug verification.

Bug Postmortem is fixing of the bugs in the program that has already crashed. It’s also a conference in which the bugs in already released application are discussed. The discussion should go without blaming.

Bug Tracking Procedure (BTP) is a list of rules about how the tester should record a bug from the time it was opened (re-opened) to the moment it was closed.

Bug Tracking System (BTS) is an application program that is created to help testers and developers to track the history of bug reports during their work. Bug trackers enable to create, store, view and modify information about bugs. The key part of such system is a data base.

Bugzilla is a free bug tracking system with web interface. It was launched in 1998. It’s open source program software.

Build is a usually pre-released version of the program. The build is created when the code is ready for implementation. One of the most important steps in a build is compilation.

Build (in BTS) is a number of the application version in which the bug was found, when the application version is 1.0-47/64, the build is 47.

Build ID is a unique identification of binaries. It’s an identifier of the application for concrete release. It can be 1.0-47/64.

Build Number specifies specific builds; one can have numerous builds for one minor version. It can be used by developers to keep track of changes and problems. In other words it’s a version of the released version.

Build Validation is a test suite that is performed on a new build in order to check its stability before the release. Build verification is done before the full test run to find the shopper defects and save testing team’s time and effort. When the build fails the build verification test testing is performed on the previous build if there is any.