Test case components (steps, expected, actual) in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What are the main components of a test case?

The main components are:
1. Test Steps: The actions to perform.
2. Expected Result: What should happen.
3. Actual Result: What actually happened during testing.

beginner

Why is the 'Expected Result' important in a test case?

It defines the correct behavior of the software. It helps testers know if the software works as intended by comparing it with the actual result.

beginner

What should you do if the Actual Result does not match the Expected Result?

You should report a defect or bug because the software is not working as expected.

beginner

Test Steps in a test case are like what in real life?

They are like a recipe or instructions you follow to bake a cake. Each step guides you to the next action.

beginner

What is the difference between Expected Result and Actual Result?

Expected Result is what should happen if the software works correctly.
Actual Result is what really happens when you run the test.

Which component of a test case describes the actions to perform?

A Test Steps

B Expected Result

C Actual Result

D Test Summary

Test Steps are the specific actions you follow to test the software.

What does the Expected Result in a test case represent?

A The correct behavior the software should show

B The list of test steps

C What actually happened during testing

D The test environment details

Expected Result defines the correct behavior or outcome expected from the software.

If the Actual Result differs from the Expected Result, what should you do?

A Ignore it

B Report a defect

C Change the Expected Result

D Skip the test

A difference means a bug or defect; it should be reported.

Which component records what really happened when running the test?

A Test Case ID

B Expected Result

C Test Steps

D Actual Result

Actual Result shows the real outcome observed during testing.

Why should test steps be clear and simple?

A To make tests longer

B To confuse testers

C So anyone can follow them easily

D To avoid writing expected results

Clear steps help testers perform tests correctly and consistently.

Explain the three main components of a test case and why each is important.

Think about what you do, what should happen, and what actually happens.

Describe what you would do if the Actual Result does not match the Expected Result during testing.

Consider how testers communicate problems.

Practice

1. Which component of a test case describes the actions a tester must perform?

easy

A. Test steps

B. Expected results

C. Actual results

D. Test summary

Solution

1. Step 1: Understand test case components

   Test cases have steps, expected results, and actual results.

2. Step 2: Identify which describes actions

   Test steps tell the tester what to do, the actions to perform.

3. Final Answer:

   Test steps -> Option A

4. Quick Check:

   Actions = Test steps [OK]

Hint: Steps = actions to perform in test case [OK]

Common Mistakes:

• Confusing expected results with steps
• Thinking actual results describe actions
• Mixing test summary with steps

2. Which of the following is the correct way to write the expected result in a test case?

easy

A. User clicks the login button and waits.

B. Click the login button to open the login page.

C. Login page appears sometimes after clicking.

D. The system should display the login page after clicking the login button.

Solution

1. Step 1: Identify expected result format

   Expected results describe what should happen clearly and precisely.

2. Step 2: Compare options

   The system should display the login page after clicking the login button. clearly states the expected system behavior after an action.

3. Final Answer:

   The system should display the login page after clicking the login button. -> Option D

4. Quick Check:

   Expected result = clear system behavior [OK]

Hint: Expected result = clear, precise system behavior [OK]

Common Mistakes:

• Writing steps instead of expected results
• Being vague or uncertain in expected results
• Mixing user actions with expected outcomes

3. Given this test case snippet:

Steps: 1. Enter username 'user1'
2. Enter password 'pass123'
3. Click 'Submit'
Expected: User is logged in and dashboard appears
Actual: Error message 'Invalid credentials'

What does this test result indicate?

medium

A. Test failed due to incorrect actual result

B. Expected result is wrong

C. Test steps are incomplete

D. Test passed successfully

Solution

1. Step 1: Compare expected and actual results

   Expected is successful login; actual shows error message.

2. Step 2: Determine test outcome

   Mismatch means test failed due to unexpected actual result.

3. Final Answer:

   Test failed due to incorrect actual result -> Option A

4. Quick Check:

   Expected ≠ Actual = Fail [OK]

Hint: If actual ≠ expected, test fails [OK]

Common Mistakes:

• Assuming test passed despite different actual result
• Confusing steps with results
• Ignoring error messages in actual results

4. A tester wrote this test case:

Steps: 1. Open app
2. Click 'Settings'
Expected: Settings page opens
Actual: Settings page opens

But the test is marked as failed. What is the most likely error?

medium

A. Steps are missing details

B. Actual result was not recorded correctly

C. Expected result is unclear

D. Test case lacks test data

Solution

1. Step 1: Check expected vs actual results

   Both say settings page opens, so results match.

2. Step 2: Consider why test marked failed

   If test failed despite matching results, actual result might be recorded incorrectly or test status set wrongly.

3. Final Answer:

   Actual result was not recorded correctly -> Option B

4. Quick Check:

   Matching results but fail = recording error [OK]

Hint: Matching expected and actual means test should pass [OK]

Common Mistakes:

• Assuming missing steps cause fail here
• Confusing unclear expected with fail reason
• Ignoring test status errors

5. You have a test case with these components:

Steps: 1. Add item to cart
2. Proceed to checkout
Expected: Total price updates correctly
Actual: Total price remains unchanged

How should you update the test case to better capture the issue?

hard

A. Remove actual result to avoid confusion

B. Change expected result to match actual price

C. Add detailed steps to verify price calculation and record exact actual price

D. Skip the test since actual differs from expected

Solution

1. Step 1: Analyze test case problem

   Actual result shows a bug: price not updating as expected.

2. Step 2: Improve test case details

   Adding detailed steps and exact actual price helps reproduce and fix the bug.

3. Final Answer:

   Add detailed steps to verify price calculation and record exact actual price -> Option C

4. Quick Check:

   More detail = better bug capture [OK]

Hint: Add details and exact actual results to clarify bugs [OK]

Common Mistakes:

• Changing expected to hide bugs
• Removing actual results loses evidence
• Skipping tests hides problems