Here is how defect is raised

1. BUG LIFE CYCLE

2. Agenda:
• What is Bug?
• What is Defect Life cycle
• Defect Workflow
• Defect Report

3. What is Bug?
• Bugs arise from mistakes and errors, made by people, in either
a program’s source code or its design
• A bug can be an error, mistake, defect or fault, which may
cause failure or deviation from expected results.

4. What is Defect life cycle:
A Defect life cycle, also known as a Bug life cycle, It is a cycle of a
defect from which it goes through covering the different states in
its entire life. This starts as soon as any new defect is found by a
tester and comes to an end when a tester closes that defect
assuring that it won’t get reproduced again.

5. Defect Workflow:

6. New: This is the first state of a defect in the Defect Life Cycle.
When any new defect is found, it falls in a ‘New’ state and
validations and testing are performed on this defect in the later
stages of the Defect Life Cycle.
Assigned: In this stage, a newly created defect is assigned to the
development team for working on the defect. This is assigned by
the project lead or the manager of the testing team to a
developer.
Open: Here, the developer starts the process of analyzing the
defect and works on fixing it, if required.

7. Fixed: When the developer finishes the task of fixing a defect by
making the required changes then he can mark the status of the
defect as ‘Fixed’.
Retest: At this point, the tester starts the task of working on the
retesting of the defect to verify if the defect is fixed accurately by
the developer as per the requirements or not.
Reopen: If any issue still persists in the defect then it will be
assigned to the developer again for testing and the status of the
defect gets changed to ‘Reopen’.
Closed: When the defect does not exist any longer then the tester
changes the status of the defect to ‘Closed’.

8. Rejected: If the defect is not considered as a genuine defect by
the developer then it is marked as ‘Rejected’ by the developer.
Duplicate: If the developer finds the defect as same as any other
defect or if the concept of the defect matches with any other
defect then the status of the defect is changed to ‘Duplicate’ by
the developer.
Deferred: If the developer feels that the defect is not of very
important priority and it can get fixed in the next releases or so in
such a case, he can change the status of the defect as ‘Deferred’.

9. Ways to Report bug:
There are two ways to report bug
1. By Defect Report
2. By Using Project management tool
• If the project is managed by using any Project management
tool then we can directly raise/open a bug in tool itself.

10. Defect Report:
• Defect report is a document that identifies and describes a
defect detected by a tester. The purpose of a defect report is to
state the problem as clearly as possible so that developers can
replicate the defect easily and fix it.
• Defect report contains Attributes/elements to report a bug
those are:
• ID: Unique identification number for the defect.
• Project name: Name of the project
• Release version: The release version of the project
• Module: Module name of the project

11. • Summary: About the defect in one line
• Description: Detailed description of the Defect including
information
• Steps to reproduce: Detailed steps along with screenshots with
which the developer can reproduce the defects
• Actual result:
• Expected result
• Severity: which describes the impact of the defect on the
application. Severity could be Blocker/major/minor/trivial
• Priority: which is related to defect fixing urgency. Priority could
be High/Medium/Low based on the impact urgency at which
the defect should be fixed respectively

12. • Reported by: Reporter name
• Assigned to: Assigned name
• Attachments: Screenshots or screen record of the defect
• Status: Status of the defect

13. Project management tools:
We have lot of tools to manage the project some of the tools are
• JIRA
• AZURE
• BUGZILLA

14. By using tool: (JIRA)

15. Any Questions?

16. Thank you!