What is a Defect Life Cycle or a Bug Lifecycle in Software Testing

Software testing is an activity of executing software or application with the intent of finding the applying bugs. It can also be stated as the procedure of validating and verifying that software application or application or product: Meets the business and technical requirements that guided it’s design and development.

System testing is an activity of executing software or application with the intent of finding the applying bugs. It can also be stated as the procedure of validating and verifying that software application or application or product: Meets the business and technical requirements that guided it’s design and development.

Defect life-cycle is a pattern which a defect goes through during its life-time. It begins when defect is discovered and finishes when a defect is shut, after guaranteeing it’s not duplicated. Defect life-cycle is relevant to the bug discovered during examining.

The bug has different declares in the Life Cycle. The Lifecycle pattern of the bug can see diagrammatically as follows:

New: When a defect is signed and published initially. It’s condition is given as new.

Assigned: After the specialist has published the bug, the cause of the specialist grants that the bug is authentic and he designates the bug to corresponding designer and the designer group. It’s condition given as allocated.

Open: At this condition the designer has began examining as well as on the defect fix.

Fixed: When designer creates necessary rule changes and confirms the changes then he/she can create bug position as ‘Fixed’ and the bug qualifies to examining group.

Awaiting retest: After solving the defect the designer has given that particular rule for retesting to the specialist. Here the testing is waiting on the evaluators end. Hence its position is awaiting retest.

Retest: At this point the specialist do the retesting of the modified rule which designer has given to him to confirm whether the defect got set or not.

Verified: The specialist assessments the bug again after it got set by the designer. If the bug is not found in the application, he grants that the bug is set and changes the position to “verified”.

Reopen: If the bug still prevails even after the bug is set by the designer, the specialist changes the position to “reopened”. The bug goes through the life-cycle once again.

Closed: Once the bug is set, it is examined by the specialist. If the specialist seems that the bug no more prevails in the application, he changes the position of the bug to “closed”. This condition indicates that the bug is set, examined and accepted.

Duplicate: If the bug is recurring twice or the two insects discuss the same idea of the bug, then one bug position is modified to “duplicate“.

Rejected: If the designer seems that the bug is not authentic, he denies the bug. Then the condition of the bug is modified to “rejected”.

Deferred: The bug, modified to postponed condition indicates the bug is predicted to be set in next produces. The factors for modifying the bug to this condition have many aspects. Some of them are concern of the bug may be low, absence of your persistence for the discharge or the bug may not have significant impact on the application.

Not a bug: The condition given as “Not a bug” if there is no change in the performance of the applying. For an example: If client requests for some modify in the look and area of the applying like modify of color of some written text then it is not a bug but just some modify in the looks of the program.

You can get Software testing job in Pune by joining any testing related training institute.

More Related Blog:

WebDriver And It’s Comparison With Selenium RC

Software Testing and Risk Analysis

Leave a Reply

Your email address will not be published. Required fields are marked *