Bird
Raised Fist0

What is the best way to write the 'Actual Result' in a bug report?

easy🧠 Conceptual Q2 of Q15
Testing Fundamentals - Test Documentation
What is the best way to write the 'Actual Result' in a bug report?
AProvide the system configuration details
BExplain what should happen ideally
CList the steps to fix the bug
DDescribe what happened when the bug occurred
Step-by-Step Solution
Solution:

  1. Step 1: Define 'Actual Result'

    This section reports what actually happened during testing, showing the bug's effect.

  2. Step 2: Differentiate from other sections

    'Expected Result' explains ideal behavior, 'Steps to fix' is for developers, 'System config' is environment info.

  3. Final Answer:

    Describe what happened when the bug occurred -> Option D

  4. Quick Check:

    Actual result = what happened [OK]
Quick Trick: Actual result = what you saw happen [OK]
Common Mistakes:
MISTAKES
  • Mixing actual and expected results
  • Writing fix instructions instead of results
  • Including environment details here

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