Scribd
Upload
3 views

Bug Defect Life Cycle

The document outlines the Bug Defect Life Cycle, detailing the stages from identifying a defect to closing it after verification. It also covers the Testing Plan, objectives, phases, requirements, design, tracking, team roles, and responsibilities to ensure effective testing. The goal of test planning is to define scope, estimate resources, identify risks, and ensure high-quality software delivery.

Uploaded by

LOVE INDIA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
3 views

Bug Defect Life Cycle

The document outlines the Bug Defect Life Cycle, detailing the stages from identifying a defect to closing it after verification. It also covers the Testing Plan, objectives, phases, requirements, design, tracking, team roles, and responsibilities to ensure effective testing. The goal of test planning is to define scope, estimate resources, identify risks, and ensure high-quality software delivery.

Uploaded by

LOVE INDIA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Bug defect life cycle

1. New: When any new defect is identified by the tester, it falls in the ‘New’ state. It is the
first state of the Bug Life Cycle. The tester provides a proper Defect document to the
Development team so that the development team can refer to Defect Document and can fix
the bug accordingly.

2. Assigned: Defects that are in the status of ‘New’ will be approved and that newly
identified defect is assigned to the development team for working on the defect and to
resolve that. When the defect is assigned to the developer team the status of the bug
changes to the ‘Assigned’ state.

3. Open: In this ‘Open’ state the defect is being addressed by the developer team and the
developer team works on the defect for fixing the bug. Based on some specific reason if the
developer team feels that the defect is not appropriate then it is transferred to either the
‘Rejected’ or ‘Deferred’ state.

4. Fixed: After necessary changes of codes or after fixing identified bug developer team
marks the state as ‘Fixed’.

5. Pending Retest: During the fixing of the defect is completed, the developer team passes
the new code to the testing team for retesting. And the code/application is pending for
retesting on the Tester side so the status is assigned as ‘Pending Retest’.

6. Retest: At this stage, the tester starts work of retesting the defect to check whether the
defect is fixed by the developer or not, and the status is marked as ‘Retesting’.
7. Reopen: After ‘Retesting’ if the tester team found that the bug continues like previously
even after the developer team has fixed the bug, then the status of the bug is again changed
to ‘Reopened’. Once again bug goes to the ‘Open’ state and goes through the life cycle again.
This means it goes for Re-fixing by the developer team.

8. Verified: The tester re-tests the bug after it got fixed by the developer team and if the
tester does not find any kind of defect/bug then the bug is fixed and the status assigned is
‘Verified’.

9. Closed: It is the final state of the Defect Cycle, after fixing the defect by the developer
team when testing found that the bug has been resolved and it does not persist then they
mark the defect as a ‘Closed’ state.

1. Testing Plan, Objectives, Testing Phases

Testing Plan

A test plan is a document that outlines:

• What will be tested

• How it will be tested

• When it will be tested

• Who will do the testing

Includes:

• Test objectives

• Test items

• Features to be tested

• Testing schedule

• Resources and team roles

Test Objectives

• To find bugs and defects

• Ensure the software works as expected

• Check that requirements are met

• Ensure product is user-friendly and secure

Testing Phases

1. Unit Testing – Testing individual code units/modules


2. Integration Testing – Testing combined modules

3. System Testing – Testing the complete application

4. Acceptance Testing – Testing by users or clients

5. Regression Testing – Retesting after code changes

6. Alpha & Beta Testing – Testing before product release

2. Bug Lifecycle

The bug lifecycle shows the steps a defect goes through:

1. New – Bug is found

2. Assigned – Assigned to a developer

3. Open – Developer starts fixing

4. Fixed – Issue is resolved

5. Retest – Tester checks again

6. Verified – If fixed, mark as verified

7. Closed – Bug is fully resolved

8. Reopened – If still not fixed, reopen

3. Testing Requirements

Testing Requirements are the foundation for creating test cases.

• Functional Requirements – What the system should do


(e.g. Login feature, user profile updates)

• Non-Functional Requirements – How the system should behave


(e.g. performance, security, usability)

Why it matters?

• Helps testers understand what to check

• Ensures complete test coverage

• Avoids missing key features during testing

4. Testing Design & Testing Tracking


Test Design

Test design means creating test cases and test scenarios.

Steps:

• Understand requirements

• Identify test conditions

• Write test cases

• Create test data

• Define expected results

Test Tracking

Test tracking means monitoring test progress and managing test activities.

Common metrics:

• Number of test cases written

• Number of test cases executed

• Number of defects found

• Test coverage %

Tools: JIRA, TestRail, Bugzilla

5. Testing Team Roles and Responsibilities

Role Responsibility

Test Manager Plans and manages overall testing activities

Test Lead Guides team, creates schedules, monitors progress

Test Engineer Writes and runs test cases

QA Analyst Ensures quality, reports bugs

Automation Tester Creates automated scripts for testing

Configuration Specialist Manages test environments and versions

6. Goal of Test Planning


Test Planning Goals:

• Define scope, approach, and objectives

• Estimate time, cost, and resources

• Identify risks and mitigation

• Assign roles and responsibilities

• Prepare tools and environments

Good test planning ensures:

• Efficient testing

• Timely delivery

• Higher quality software

You might also like