Test case components (steps, expected, actual) in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Identify the correct expected result in a test case

You have a test case for a login feature. The test steps are:
1. Open the login page.
2. Enter valid username and password.
3. Click the login button.
What should be the expected result?

A The user is redirected to the dashboard page.

B The login button becomes disabled.

C The system displays an error message about invalid credentials.

D The username and password fields are cleared.

💡 Hint

Think about what should happen when valid credentials are entered.

The expected result describes what should happen if the test steps are followed correctly. For a successful login, the user should be redirected to the dashboard page.

❓ assertion

intermediate

Choose the correct actual result for a failed test

A test case checks if a search function returns results for a keyword. The expected result is:
Search results related to the keyword are displayed.
After running the test, the search page shows a message: 'No results found'. What is the actual result?

A Search results related to the keyword are displayed.

B The search page shows a message: 'No results found'.

C The search button is disabled.

D The page reloads without any message.

💡 Hint

The actual result is what you observe after running the test steps.

The actual result is the real outcome after executing the test. Here, the page shows 'No results found', which differs from the expected result.

❓ Predict Output

advanced

What is the output of this test step log?

Consider this test step log snippet from an automated test:

1. Navigate to homepage
2. Click 'Sign Up' button
3. Enter email: '[e-mail]'
4. Click 'Submit'
5. Verify confirmation message

The test fails at step 5 with the message: 'Expected: "Thank you for signing up!" Actual: "Error: Email already exists."'. What is the test result?

A Test failed because the actual message differs from expected.

B Test passed because the confirmation message appeared.

C Test passed because the email was entered correctly.

D Test failed because the 'Submit' button was not clicked.

💡 Hint

Compare the expected and actual messages carefully.

The test fails because the actual confirmation message does not match the expected one. This indicates a problem with the signup process.

🔧 Debug

advanced

Find the missing component in this test case

Here is a test case outline for a password reset feature:

Test Steps:
1. Open the password reset page.
2. Enter registered email.
3. Click 'Reset Password'.

Which component is missing to make this a complete test case?

A Actual result observed after running the test.

B Test case ID and author information.

C Expected result describing what should happen after clicking 'Reset Password'.

D Test data such as the registered email address.

💡 Hint

Think about what tells you if the test passed or failed.

The expected result is essential to know what outcome to look for after performing the test steps. Without it, you cannot judge success or failure.

❓ framework

expert

Which test case component best supports automated test reporting?

In an automated testing framework, which test case component is most critical for generating clear test reports that show pass or fail status?

A Test steps detailing each action to perform.

B Expected results defining the correct behavior.

C Test case description explaining the test purpose.

D Actual results captured during test execution.

💡 Hint

Think about what the test runner records to decide pass or fail.

Actual results recorded during execution allow the framework to compare against expected results and generate pass/fail reports automatically.

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