Use case testing in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is use case testing?

Use case testing is a technique where tests are designed based on real-world scenarios or user interactions with the system to verify that the system behaves as expected.

beginner

Why is use case testing important?

It helps ensure the software meets user requirements by focusing on how users will actually use the system, catching issues that might not appear in other testing methods.

intermediate

What are the main components of a use case?

A use case typically includes the actor (user or system), the goal or task, the steps to achieve the goal, and possible alternative flows or exceptions.

intermediate

How does use case testing differ from functional testing?

Use case testing focuses on user scenarios and end-to-end flows, while functional testing checks individual functions or features in isolation.

beginner

Give an example of a use case test scenario.

For an online shopping site: A user logs in, searches for a product, adds it to the cart, and completes the purchase. The test checks if all these steps work smoothly together.

What does use case testing primarily focus on?

A User interactions and scenarios

B Code syntax errors

C Database performance

D Network security

Use case testing is about testing real user scenarios to ensure the system behaves as expected.

Which of the following is NOT a part of a use case?

A Actor

B Goal

C Code implementation details

D Alternative flows

Use cases focus on user goals and flows, not on code details.

Use case testing helps to catch issues that might be missed by:

A All of the above

B Integration testing

C Functional testing

D Unit testing

Use case testing covers end-to-end user scenarios, which can reveal issues missed by other testing types.

Which scenario best represents a use case test?

A Testing if a login button appears on the page

B Checking if a user can log in, browse products, and checkout successfully

C Verifying database connection speed

D Reviewing code comments

Use case testing checks complete user workflows, like logging in and completing a purchase.

What is an actor in use case testing?

A A database table

B A software developer

C A test script

D A user or system interacting with the software

An actor is the user or system that performs actions in the use case.

Explain what use case testing is and why it is useful.

Think about how users interact with software in real life.

Describe the main parts of a use case and how they help in designing tests.

Consider what information you need to test a user story.

Practice

1. What is the main purpose of use case testing in software testing?

easy

A. To find syntax errors in the source code

B. To verify software behavior by simulating real user actions step-by-step

C. To test only the software's performance under load

D. To check the software's internal code structure

Solution

1. Step 1: Understand use case testing focus

   Use case testing simulates how users interact with software in real scenarios.

2. Step 2: Compare options to definition

   Only To verify software behavior by simulating real user actions step-by-step describes testing by following user actions step-by-step.

3. Final Answer:

   To verify software behavior by simulating real user actions step-by-step -> Option B

4. Quick Check:

   Use case testing = user action simulation [OK]

Hint: Think: Does it test user steps or internal code? [OK]

Common Mistakes:

• Confusing use case testing with code structure testing
• Thinking it tests performance or syntax only
• Ignoring the step-by-step user action focus

2. Which of the following is the correct way to write a use case test step?

easy

A. User logs in with valid username and password.

B. Check if login button is blue.

C. Verify database connection string.

D. Run performance test for login page.

Solution

1. Step 1: Identify use case test step format

   Use case steps describe user actions in simple sentences.

2. Step 2: Match options to format

   User logs in with valid username and password. describes a user action clearly; others focus on UI color, backend, or performance.

3. Final Answer:

   User logs in with valid username and password. -> Option A

4. Quick Check:

   Use case step = user action sentence [OK]

Hint: Look for user action description, not technical checks [OK]

Common Mistakes:

• Choosing UI or backend checks as use case steps
• Confusing performance tests with use case steps
• Writing vague or non-action statements

3. Given this use case test step: User enters invalid password and clicks login, what is the expected result?

medium

A. Application crashes.

B. User is logged in successfully.

C. Error message 'Invalid password' is shown.

D. Password field clears automatically.

Solution

1. Step 1: Analyze the test step

   The user enters an invalid password and tries to log in.

2. Step 2: Determine expected behavior

   The system should reject invalid passwords and show an error message.

3. Final Answer:

   Error message 'Invalid password' is shown. -> Option C

4. Quick Check:

   Invalid input = error message shown [OK]

Hint: Invalid input usually triggers error messages [OK]

Common Mistakes:

• Assuming invalid input logs in user
• Expecting app crash on invalid input
• Thinking fields clear automatically without prompt

4. A use case test step says: User clicks 'Submit' without filling required fields. The test fails because the form submits anyway. What is the likely error?

medium

A. The validation step for required fields is missing or incorrect.

B. The submit button is disabled.

C. The user entered all fields correctly.

D. The form resets after submission.

Solution

1. Step 1: Understand the failure

   The form submits even when required fields are empty, which is wrong.

2. Step 2: Identify cause

   Missing or faulty validation allows submission without required data.

3. Final Answer:

   The validation step for required fields is missing or incorrect. -> Option A

4. Quick Check:

   Missing validation = form submits wrongly [OK]

Hint: Check if validation steps exist for required fields [OK]

Common Mistakes:

• Assuming submit button disables automatically
• Ignoring missing validation logic
• Confusing form reset with submission failure

5. You have a use case testing scenario for an online store checkout:
1. User adds item to cart
2. User proceeds to checkout
3. User enters invalid credit card number
4. User clicks 'Pay'
Which expected result best fits this use case test?

hard

A. Payment is processed successfully.

B. Cart is emptied automatically.

C. User is redirected to homepage without message.

D. Error message 'Invalid credit card number' is displayed and payment is blocked.

Solution

1. Step 1: Review the scenario steps

   User tries to pay with an invalid credit card number.

2. Step 2: Determine correct system response

   The system should block payment and show an error about the invalid card.

3. Final Answer:

   Error message 'Invalid credit card number' is displayed and payment is blocked. -> Option D

4. Quick Check:

   Invalid payment info = error shown, payment blocked [OK]

Hint: Invalid payment info must trigger error and block payment [OK]

Common Mistakes:

• Assuming payment succeeds with invalid data
• Expecting silent redirects without messages
• Thinking cart empties on failed payment