Defect Reporting

Question 1

How can we determine if we’ve found a defect?

Answer 1

If expected result mismatches actual result, we can confidently say we’ve found a defect.

Question 2

The definition of Defect.

Answer 2

An imperfection or deficiency in a work product where it does not meet its requirements or specifications.

Question 3

The definition of Expected result.

Answer 3

The predicted observable behavior of a component or system executing under specified conditions, based on its specification or another source.

Question 4

The definition of Actual result.

Answer 4

The behavior produced or observed when a component or system is tested.

Question 5

What is a defect report?

Answer 5

Documentation of the occurence, nature, and status of a defect.

Question 6

What should a defect report do?

Answer 6

~ Describe the issue in details
~ Define the severity and priority of the issue
~ Provide all necessary data to reproduce and fix the issue
~ Help developer to fix the issue

Question 7

What is the main goal of a defect report?

Answer 7

The main goal of a defect report is to get the defect fixed.

Question 8

How can you recognize a good defect report?

Answer 8

Good defect report:
~ Provides significant details
~ Easy and obvious
~ Facilitates quick and easy solutions

Question 9

List main statuses of defect report during its lifecycle.

Answer 9

~ Submitted (Can be later Assigned, Declined or Deferred)
~ Assigned (Can be later Fixed or Declined)
~ Fixed (Can be later Verified or Reopened)
~ Verified (Can be later Closed)
~ Closed (Can be later Reopened)
~ Reopened (Can be later Assigned or Declined)
~ Declined (Can be later Reopened)
~ Deferred (Can be later Submitted or Reopened)

Question 10

List all key defect report fields.

Answer 10

1. ID
2. Summary
3. Description
4. Steps to reproduce
5. Reproducibility
6. Severity
7. Priority
8. Symptom
9. Workaround
10. Comments
11. Attachments

Question 11

Elaborate. Key defect report field: ID

Answer 11

~ Unique

~ Meaningful (if bug tracking system allows)

Question 12

Elaborate. Key defect report field: Summary

Answer 12

~ Answers questions:
    ~ What did happen?
    ~ Where did it happen?
    ~ In what conditions did it happen?
~ Should at the same time:
    ~ Provide as much information as possible
    ~ Be as short as possible/Be Concise
    ~ Be easily distinguishable from other summaries

Question 13

Elaborate. Key defect report field: Description

Answer 13

~ Contains detailed defect description
~ Unlike Summary, Description may be as long as it needs to be informative
~ In many BTS testers use Description to write down the actual result and the reference to the corresponding requirement

Question 14

Elaborate. Key defect report field: Steps to reproduce

Answer 14

~ Contains detailed description of actions to be done to reproduce the defect
~ May contain a short description of the defect or the final erroneous state of the app

Question 15

Elaborate. Key defect report field: Reproducibility

Answer 15

~ Shows if the defect appear each time we follow steps to reproduce (“Always”), or if the defect sometimes appears and sometimes doesn’t (“Sometimes”)
~ Defects with the reproducibility “Always” are much more easier to fix

Question 16

Elaborate. Key defect report field: Severity

Answer 16

~ Shows the damage the defect causes
~ Typical values are:
    ~ Critical
    ~ Major
    ~ Medium
    ~ Minor

Question 17

Elaborate. Key defect report field: Priority

Answer 17

~ Shows the urgency to fix the defect
~ Typical values are:
    ~ ASAP
    ~ High
    ~ Normal
    ~ Low

Question 18

Elaborate. Key defect report field: Symptom

Answer 18

~ Allows defects classification by typical indication

Question 19

Elaborate. Key defect report field: Workaround

Answer 19

~ Shows if there is a way to achieve the desired result without being interrupted by the defect
~ Typical values are “Yes” and “No”

Question 20

Elaborate. Key defect report field: Comments

Answer 20

~ Optional field

~ May contain any data useful to the process of bug fixing

Question 21

Elaborate. Key defect report field: Attachments

Answer 21

~ Optional field

~ May contain any files, screenshots, etc. useful to the process of bug fixing