Bird
Raised Fist0

Why is it important to include both 'Expected Result' and 'Actual Result' in a bug report?

hard🧠 Conceptual Q10 of Q15
Testing Fundamentals - Test Documentation
Why is it important to include both 'Expected Result' and 'Actual Result' in a bug report?
ATo clearly show the difference between intended and observed behavior
BTo provide steps to fix the bug
CTo list all software versions installed
DTo describe the user interface design
Step-by-Step Solution
Solution:

  1. Step 1: Understand the role of Expected and Actual Results

    Expected Result shows what should happen; Actual Result shows what did happen.

  2. Step 2: Explain importance

    Showing both highlights the bug clearly by contrasting intended vs observed behavior.

  3. Final Answer:

    To clearly show the difference between intended and observed behavior -> Option A

  4. Quick Check:

    Expected vs Actual = difference shows bug [OK]
Quick Trick: Expected and Actual show bug difference [OK]
Common Mistakes:
MISTAKES
  • Confusing results with fix instructions
  • Listing software versions here
  • Describing UI design instead

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Testing Fundamentals Quizzes
Non-Functional Testing - Security testing basics - Quiz 2easy Test Documentation - Test strategy document - Quiz 8hard Test Documentation - Test plan structure - Quiz 10hard Test Documentation - Why documentation ensures repeatability - Quiz 4medium Testing Models and Approaches - Shift-left testing - Quiz 10hard Testing Models and Approaches - Shift-left testing - Quiz 1easy Testing Models and Approaches - Black-box vs white-box testing - Quiz 1easy Testing Models and Approaches - Why testing approaches guide strategy - Quiz 4medium Testing Types and Levels - Why different testing levels catch different bugs - Quiz 9hard Why Software Testing Matters - Why testing prevents costly failures - Quiz 5medium