3.2. When to Report a Defect?

Try these first

1. 1.

   Define what a defect is in the context of software testing.

   Hint

   Think about the difference between expected vs. actual results.

2. 2.

   List two reasons why defects should be reported.

   Hint

   Consider the implications for users if defects are not reported.

3. 3.

   What is a defect?

   • A planned feature
   • An unexpected behavior
   • A successful test case

   Hint

   Think about the opposite of what you intend to happen in software.

4. 4.

   True or False: It is unnecessary to report defects that have low severity.

   • True
   • False

   Hint

   Consider the cumulative effect of multiple low-severity defects.

5. 5.

   You are a tester who found a critical defect that could compromise user data security. Outline what you would include in your defect report.

   Hint

   Think about all aspects of data security and what you feel is urgent.

6. 6.

   You’re in a team meeting to discuss defects found during testing. How would you prioritize defects, and what criteria would you use?

   Hint

   Use examples from prior defects you've encountered to illustrate your points.