What is a Bug and its Life Cycle?

The first thing people who decided to start working in the software testing field face, is the bug phenomenon. Commonly if the system doesn’t work consequently to user’s waiting, it can be a bug.  Let’s look at this concept in more detail.

Usually a bug is a deflection from the requirement that is determined for the software. For example, performing functional testing for a website a tester finds out that a button for registration is not clickable or redirects user to another website but not to the Registration form. Such a behavior is incorrect so tester can consider it to be a bug.

Bug’s life cycle is a term from the moment of its detection till its resolution. Every type of testing – mobile application testing, website testing or desktop testing – assumes detection and processing a defect in view of all embodiments outcome.

4 Common Variants of Bug Been Handled:

1. Tester detects bug and Project Manager rejects it;
2. Project Manager approves the bug and redirects it to the development department, where it is rejected;
3. Development department confirms the ticket, fixes an error and send to the tester for reexamination. If the bug is still reproducing the tester reopens the ticket;
4. After receiving a notification from the development team about error’s hotfix tester performs verification once more. If the bug is not reproducing – the ticket is closed.

Every bug must be documented taking into account its whole life cycle, as it can be of great importance for customers or developers in future. For example, for black-box testing of the product, if the similar one was earlier tested, in consideration of absence of any other documentation.

 Source: QATestLab