Defect life cycle is a cycle which a defect goes through during its lifetime. It starts when defect is found and ends when a defect is closed, after ensuring it's not. Nindel-Edwards, Jim and Steinke, Gerhard () "A Full Life Cycle Defect intersection of the defect process with the project life cycle is best seen with a. Mistakes lead to the introduction of defects (also called bugs). Because defects can be introduced anywhere in the life cycle, in any work product, and because.
|Language:||English, Spanish, Dutch|
|Genre:||Business & Career|
|ePub File Size:||15.59 MB|
|PDF File Size:||10.80 MB|
|Distribution:||Free* [*Register to download]|
Defect life cycle, also known as Bug Life cycle is the journey of a defect cycle, which a defect goes through during its lifetime. It varies from organization to. The tester opens a bug and assigns it to the bug coordinator from a predefined list. The bug coordinator assigns the bug to the R&D team leader and the bug. This tutorial describes the various stages in a bug aka defect life cycle and its importance.
Recommended Reading What is Defect? A Defect, in simple terms, is a flaw or an error in an application that is restricting the normal flow of an application by mismatching the expected behavior of an application with the actual one. The defect occurs when any mistake is made by a developer during the designing or building of an application and when this flaw is found by a tester, it is termed as a defect. It is the responsibility of a tester to do a thorough testing of an application with an intention to find as many defects as possible so as to ensure that a quality product will reach the customer. It is important to understand about defect life cycle before moving to the workflow and different states of the defect. Hence, let's take know more about Defect Life Cycle.
Defect Life Cycle or Bug Life Cycle is the specific set of states that a Bug goes through from discovery to defect fixation.
Bug Life Cycle Status The number of states that a defect goes through varies from project to project. Below lifecycle diagram, covers all possible states New: When a new defect is logged and posted for the first time.
It is assigned a status as NEW. Assigned: Once the bug is posted by the tester, the lead of the tester approves the bug and assigns the bug to the developer team Open: The developer starts analyzing and works on the defect fix Fixed: When a developer makes a necessary code change and verifies the change, he or she can make bug status as "Fixed.
Since the software testing remains pending from the testers end, the status assigned is "pending request. If there is no bug detected in the software, then the bug is fixed and the status assigned is "verified. Once again the bug goes through the life cycle. Closed: If the bug is no longer exists then tester assigns the status "Closed.
Defect Life Cycle Explained Status assigned to defect- New A defect is forwarded to Project Manager for analyze Project Manager decides whether a defect is valid Here the defect is not valid- a status is given "Rejected. If the defect is not rejected then the next step is to check whether it is in scope. Suppose we have another function- email functionality for the same application, and you find a problem with that.
The mandatory fields when a tester logs any new bug are Build version, Submit On, Product, Module, Severity, Synopsis and Description to Reproduce In above list, you can add some optional fields if you are using manual Bug submission template. Otherwise, Test manager will set status, Bug priority and assign the bug to the respective module owner.
Look at the following Defect cycle: The above image is quite detailed and when you consider the significant steps in bug life cycle you will get a quick idea about it. On successful logging, the bug is reviewed by Development or Test manager.
Test manager can set the bug status as Open, can Assign the bug to developer or bug may be deferred until next release. If the bug is fixed then QA verifies the bug and can set the bug status as verified closed or Reopen. Guidelines for Implementing Defect Life Cycle There are some important guidelines which can be adopted before starting to work with defect life cycle.
These are as follows: It is very important that before starting to work on the defect life cycle, the whole team clearly understands the different states of a defect discussed above.
Defect Life Cycle should be properly documented to avoid any confusion in the future.
Each individual who is changing the status of a defect should be properly aware of that status and should provide enough details about the status and the reason for putting that status so that everyone who is working on that particular defect can understand the reason of such a status of a defect very easily. Defect tracking tool should be handled with care to maintain the consistency among the defects and thus, in the workflow of the defect life cycle.
Next, let's discuss the interview questions based on the defect life cycle.
Ans: A defect is any kind of flaw or error in the application that is restricting the normal flow of an application by mismatching the expected behavior of an application with the actual one. Q 2 What is the major difference between Error, Defect, and Failure?
Ans: Error: If the developers find that there is a mismatch in the actual and expected behavior of an application in the development phase then they call it as an Error.
Defect: If testers find a mismatch in the actual and expected behavior of an application in the testing phase then they call it as a Defect. Failure: If customers or end users find a mismatch in the actual and expected behavior of an application in the production phase then they call it as a Failure.
Q 3 What is the status of a defect when it is initially found? This is the initial state of a newly found defect.
Q 4 What are the different states of a defect in the defect life cycle when a defect is approved and fixed by a developer? Q 5 What happens if a tester still finds an issue in the defect that is fixed by a developer?