Defect Management Questions and Answers

1.     Why is defect management process important in software development teams?

Ans: Defect management process is important in software development teams because developers will be able to determine the importance or the impact of the defect. The process also can prevent defects; implementation of test techniques, methodology and standard processes to reduce the risk of defects. By following the defect management process, the software developers are able to categorize/prioritize the defect if this needs fixing straight away or this can wait until the next releases. This also can improve the development process as this can prevent the defects from occurring again.

2.     What are the fields in the bug report?

Ans: Bug ID, Bug Description, Version, Steps, Date Raised, Reference, Detected By, Status, Fixed By, Date Closed, Severity and Priority

3.     Why do defects have priority and severity?

Ans: Priority and severity are important in raising defects as these two category will determine how important the bug to be fixed. These categorize the importance or the impact of the defect of the software.

4.     When does a defect gets deferred?

Ans: A defect gets deferred if the developer feels that the bug is not a prime priority then defect gets deferred. The deferred bugs/defects can be fixed in the next releases.

5.     How do you deal with an inconsistent defect?

Ans: By logging a defect with a screenshot or video attached on it.

6.      How do you log a defect?

Ans: By capturing the detailed information of how you find the defect by writing in detailed steps and following the bug reports template of the defect management software used. You can either attach a screenshot or a video to support your report.

7.     Can you name a defect that has a high priority and low severity?

Ans: A logo error on your website. It is a low severity as it won’t affect the functionality of your website but high priority as you don’t want your client to see an incorrect logo on your website.

8.     When does a defect gets rejected by the developer?

Ans: A defect get rejected by the developer if the defect raised is out of scope of the requirement, lack of test data, non-reproducible or duplicate bugs.

9.     What is a change request and how does a change request gets handled?

Ans: Change request is a proposal to alter a product or system. To handle the change request is to have a right processes in place to manage them. In that way, everyone in the development team is within the loop and will be able to follow the workflow.

10.   How do you analyse the root cause of a defect?

Ans: To analyse the root cause of a defect is by determining the what, how and why the defect occurred so that can be taken to prevent future occurences.

11.   What is defect triaging?

Ans: Defect Triaging is a process where each bug is prioritized based on its severity. It is to evaluate, prioritize and assign the resolution of the defect.