Solution:Step 1: Understand the discrepancySuccess message appeared but data not updated, indicating a backend issue.Step 2: Determine appropriate actionInvestigate backend processes and logs to find root cause.Step 3: Eliminate incorrect optionsMarking failed without investigation is premature; ign

[Solved] A test case shows:Steps: 1. Go to account settings2. Change phone number to '1234567890'3. Save changesExpected: Success message displayedActual:... | Testing Fundamentals

Testing Fundamentals - Test Documentation

A test case shows:
Steps: 1. Go to account settings
2. Change phone number to '1234567890'
3. Save changes
Expected: Success message displayed
Actual: Success message displayed
Later, the phone number was not updated in the system. What is the best next step?

AMark test as failed immediately

BReview backend update process and logs

CIgnore since success message appeared

DChange expected result to match actual

Step-by-Step Solution

Solution:

Step 1: Understand the discrepancy
Success message appeared but data not updated, indicating a backend issue.
Step 2: Determine appropriate action
Investigate backend processes and logs to find root cause.
Step 3: Eliminate incorrect options
Marking failed without investigation is premature; ignoring is wrong; changing expected result hides defect.
Final Answer:
Review backend update process and logs -> Option B
Quick Check:
Investigate root cause beyond UI messages [OK]

Quick Trick: Investigate backend if UI shows success but data incorrect [OK]

Common Mistakes:

Assuming test passed because of success message
Changing expected results to hide defects

Master "Test Documentation" in Testing Fundamentals

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Trace Try Challenge Automate Recall Frame

More Testing Fundamentals Quizzes

A test case shows:

Step 1: Understand the discrepancy

Step 2: Determine appropriate action

Step 3: Eliminate incorrect options

Final Answer:

Quick Check:

Want More Practice?