Manual Testing Course-Day 11

 

What is Defect Life Cycle?

Defect Life Cycle or Bug Life Cycle in software testing is the specific set of states that defect or bug goes through in its entire life. The purpose of Defect life cycle is to easily coordinate and communicate current status of defect which changes to various assignees and make the defect fixing process systematic and efficient.

Defect Status

Defect Status or Bug Status in defect life cycle is the present state from which the defect or a bug is currently undergoing. The goal of defect status is to precisely convey the current state or progress of a defect or bug in order to better track and understand the actual progress of the defect life cycle.

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."
  • Pending retest: Once the defect is fixed the developer gives a particular code for retesting the code to the tester. Since the software testing remains pending from the testers end, the status assigned is "pending retest."
  • Retest: Tester does the retesting of the code at this stage to check whether the defect is fixed by the developer or not and changes the status to "Re-test."

Defect Life Cycle

  • Verified: The tester re-tests the bug after it got fixed by the developer. If there is no bug detected in the software, then the bug is fixed and the status assigned is "verified."
  • Reopen: If the bug persists even after the developer has fixed the bug, the tester changes the status to "reopened". Once again the bug goes through the life cycle.
  • Closed: If the bug is no longer exists then tester assigns the status "Closed." 
  • Duplicate: If the defect is repeated twice or the defect corresponds to the same concept of the bug, the status is changed to "duplicate."
  • Rejected: If the developer feels the defect is not a genuine defect then it changes the defect to "rejected."
  • Deferred: If the present bug is not of a prime priority and if it is expected to get fixed in the next release, then status "Deferred" is assigned to such bugs
  • Not a bug:If it does not affect the functionality of the application then the status assigned to a bug is "Not a bug".

Defect Life Cycle Explained

Defect Life Cycle or Bug Life Cycle - Stuff You Must Know!

    1. Tester finds the defect
    2. Status assigned to defect- New
    3. A defect is forwarded to Project Manager for analyze
    4. Project Manager decides whether a defect is valid
    5. Here the defect is not valid- a status is given "Rejected."
    6. So, project manager assigns a status 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. But it is not a part of the current release when such defects are assigned as a postponed or deferred status.
    7. Next, the manager verifies whether a similar defect was raised earlier. If yes defect is assigned a status duplicate.
    8. If no the defect is assigned to the developer who starts fixing the code. During this stage, the defect is assigned a status in- progress.
    9. Once the code is fixed. A defect is assigned a status fixed
    10. Next, the tester will re-test the code. In case, the Test Case passes the defect is closed. If the test cases fail again, the defect is re-opened and assigned to the developer.
    11. Consider a situation where during the 1st release of Flight Reservation a defect was found in Fax order that was fixed and assigned a status closed. During the second upgrade release the same defect again re-surfaced. In such cases, a closed defect will be re-opened.

That's all to Bug Life Cycle

____________________________________________




Comments

Post a Comment

Popular posts from this blog

Manual Testing Course-Day 13

Image
  Manual Testing Manual testing  is a software  testing  process in which  test  cases are executed  manually  without using any automated tool. All  test  cases executed by the tester  manually  according to the end user's perspective. It ensures whether the application is working, as mentioned in the requirement document or not. What is Automation Testing? Automation testing is a Software testing technique to test and compare the actual outcome with the expected outcome. This can be achieved by writing test scripts or using any automation testing tool. Test automation is used to automate repetitive tasks and other testing tasks which are difficult to perform manually.  Performance Testing Performance Testing  is a software testing process used for testing the speed, response time, stability, reliability, scalability and resource usage of a software application under particular workload. The main purpose of performan...
Read more

Manual Testing Course-Day 5

Image
  Test Plan A  TEST PLAN  is a document describing software testing scope and activities. It is the basis for formally testing any software / product in a project. ISTQB Definition test plan : A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, the features to be tested, the testing tasks, who will do each task, degree of tester independence, the test environment, the test design techniques and entry and exit criteria to be used, and the rationale for their choice,and any risks requiring contingency planning. It is a record of the test planning process. master test plan : A test plan that typically addresses multiple test levels. phase test plan : A test plan that typically addresses one test phase. Elaboration Test Plan is influenced by  the following factors: Organizational test policy and test strategy Software development life cycle model Scope of testing Availability of resources...
Read more

Manual Testing Course -Day-2

Image
Software Testing Life Cycle (STLC) Software Testing Life Cycle (STLC)  is a sequence of specific activities conducted during the testing process to ensure software quality goals are met. STLC involves both verification and validation activities. Contrary to popular belief, Software Testing is not just a single/isolate activity, i.e. testing. It consists of a series of activities carried out methodologically to help certify your software product. STLC stands for Software Testing Life Cycle. STLC Phases Requirement Analysis Test Planning Test Case Development Test Environment Setup Test Execution Test Cycle Closure STLC Phases along with Entry and Exit Criteria STLC Phases There are following six major phases in every Software Testing Life Cycle Model (STLC Model): Requirement Analysis Test Planning Test case development Test Environment setup Test Execution Test Cycle closure STLC Model Phases Each of these stages has a definite Entry and Exit criteria, Activities & Deliverables...
Read more