Software Defect Reporting
Interview Questions on Defect Reporting
1) What is Defect in Software Testing?
A flaw in a component or system that can cause the component or system to fail to perform its required function, e.g. an incorrect statement or data definition. A defect, if encountered during execution, may cause a failure of the component or system.
2) Differentiate Error, Defect, and Failure?
Terminology vary from one phase to another in Software Application Life Cycle
Software Application Life Cycle has 3 phases;
i) Development phase
in Development phase if developers find any mismatch they call it as Error or mistake
ii) Testing phase
In Testing phase if Testers find any mismatch they call it as Defect or Bug or Fault
iii) Production phase
In Production phase if Customers or End Users find any mismatch they call it as Failure
3) Give a sample Defect report template?
A Sample Defect Report Template:
1) Defect ID: Unique No or Name
2) Description: Summary of the defect
3) Feature: Module / Function / Service , in these module TE found the defect
4) Test Case Name: Corresponding failing test condition
5) Reproducible (Yes / No): Yes -> Every time defect appears during test execution
No -> Rarely defect appears
If Yes, attach test procedure:
If No, attach snapshot & strong reasons:
6) Status: New / Reopen
7) Severity: Seriousness of defect w.r.t functionality (high / medium / low)
8) Priority: Importance of the defect w.r.t customers (high / medium / low)
9) Reported bug: Name of Test Engineer
10) Reported on: Date of submission
11) Assign to: Name of the responsible person in development team -> PM
12) Build Version ID: In which build, Test Engineer fount the defect
13) Suggested fix (Optional): Tester tries to produce suggestion to solve this defect
14) Fixed by: PM or Team Lead
15) Resolved by: Developer name
16) Resolved on: Date of solving By Developers
17) Resolution type: check out in next page
18) Approved by: Signature of Project Manager (PM)
Note: Defect Report Template may vary from one company to another and one project to another
4) What is producible defect?
If a Defect is appearing every time (in every execution) then that Defect is producible defect, we can provide steps for locating it.
5) What is not reproducible defect?
If a Defect is some time times only appearing then that Defect is not producible defect, we have to provide proof (snap shots or database dumps) for locating it.
6) What are the different types of Status of Defects?
Status of Defects
New: Tester provides new status while Reporting (for the first time)
Open: Developer / Dev lead /DTT opens the Defect
Rejected: Developer / Dev lead /DTT rejects if the defect is invalid or defect is duplicate.
Fixed: Developer provides fixed status after fixing the defect
Deferred: Developer provides this status due to time etc…
Closed: Tester provides closed status after performing confirmation Testing
Re-open: Tester Re-opens the defect with valid reasons and proofs
7) Explain about Defect Life Cycle?
Defect Life Cycle
Different Flows of the Defect
a) New > Opened > Closed
b) New > Opened > Closed
c) New > Opened > Fixed > Re-Opened > Fixed > Closed
d) New > Opened > Deferred
e) New > Opened > Rejected > Re-Opened > Fixed > Closed
8) What is Defect Management?
The process of recognizing, investigating, taking action and disposing of defects. It involves recording defects, classifying them and identifying the impact.
Some companies use Manual Process (Excel workbook), and some companies use Tool based process for Defect Management.
Bugzilla / Issue-Tracker / PR-Tracker/Jira / Quality Center etc…(anyone)
9) What is Defect Management Tool?
A tool that facilitates the recording and status tracking of defects and changes. They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of defects and provide reporting facilities.
10) What is Defect Deduction Percentage (DDP)?
The number of defects found by a test phase, divided by the number found by that test phase and any other means afterwards.
11) What is the Defect Reporting Process?
Defect Reporting Process may vary from one company to another
Defect Reporting Process
Defect Reporting Process vary from one company to another.
a) Small scale Company
Tester -> Developer
b) Medium scale Company
Tester -> Test Lead -> Development Lead -> Developer
c) Large scale Company
Tester -> Test Lead -> DTT -> Development Lead -> Developer
12) What is Defect Masking?
An occurrence in which one defect prevents the detection of another.
13) What is Defect Density?
The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms, e.g. lines-ofcode, number of classes or function points).
14) What is Defect Based Test Design Technique?
A procedure to derive and/or select test cases targeted at one or more defect categories, with tests being developed from what is known about the specific defect category.
15) What is Defect Report?
A document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function.