Bird
0
0

In a bug report, the 'Expected Result' says 'Page loads in 2 seconds', but the tester wrote 'Page loads fast'. What is the issue?

medium📝 Debug Q7 of 15
Testing Fundamentals - Test Documentation
In a bug report, the 'Expected Result' says 'Page loads in 2 seconds', but the tester wrote 'Page loads fast'. What is the issue?
AExpected Result is too detailed
BExpected Result is vague and not measurable
CActual Result should be written instead
DSteps to Reproduce are missing
Step-by-Step Solution
Solution:

  1. Step 1: Analyze the Expected Result wording

    'Page loads fast' is subjective and unclear, making it hard to verify.

  2. Step 2: Identify the problem

    Expected Result should be specific and measurable, like 'Page loads in 2 seconds'.

  3. Final Answer:

    Expected Result is vague and not measurable -> Option B

  4. Quick Check:

    Expected result must be clear and measurable [OK]
Quick Trick: Expected result must be specific and measurable [OK]
Common Mistakes:
  • Writing vague expected results
  • Confusing actual and expected results
  • Ignoring missing reproduction steps

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Testing Fundamentals Quizzes
Functional Testing Techniques - Why systematic techniques improve coverage - Quiz 1easy Functional Testing Techniques - Exploratory testing - Quiz 11easy Functional Testing Techniques - State transition testing - Quiz 3easy Non-Functional Testing - Compatibility testing - Quiz 15hard Test Documentation - Why documentation ensures repeatability - Quiz 1easy Testing Models and Approaches - Why testing approaches guide strategy - Quiz 14medium Testing Models and Approaches - Shift-left testing - Quiz 4medium Testing Types and Levels - Why different testing levels catch different bugs - Quiz 12easy Why Software Testing Matters - Tester mindset and thinking - Quiz 2easy Why Software Testing Matters - Testing vs debugging distinction - Quiz 3easy