Use case testing in Testing Fundamentals - Framework Patterns

Framework Mode - Use case testing

Folder Structure for Use Case Testing Framework

use_case_testing_project/
├── use_cases/               # Documents describing use cases
│   ├── login_use_case.md
│   ├── purchase_use_case.md
│   └── profile_update_use_case.md
├── tests/                   # Automated test scripts based on use cases
│   ├── test_login.py
│   ├── test_purchase.py
│   └── test_profile_update.py
├── utilities/               # Helper functions and utilities
│   └── helpers.py
├── config/                  # Configuration files for environments
│   └── config.yaml
├── reports/                 # Test execution reports
│   └── latest_report.html
└── README.md                # Project overview and instructions

Test Framework Layers for Use Case Testing

• Use Case Documents: Written descriptions of user interactions and expected outcomes. These guide test creation.
• Test Scripts: Automated tests that follow the steps in the use cases to verify the system behaves as expected.
• Utilities: Helper functions to support test scripts, such as data setup or common actions.
• Configuration: Settings for different environments, test data, or parameters to run tests flexibly.
• Reports: Output from test runs showing which use cases passed or failed.

Configuration Patterns for Use Case Testing

Use a config.yaml file to store environment details like URLs, credentials, and test data. This allows running the same use case tests in different environments without changing code.

environment: staging
base_url: https://staging.example.com
credentials:
  user: testuser
  password: password123

Load this config in test scripts to keep tests flexible and maintainable.

Test Reporting and CI/CD Integration

• Generate clear reports after test runs showing which use cases passed or failed.
• Use simple HTML or XML reports for easy reading and sharing.
• Integrate tests into CI/CD pipelines to run use case tests automatically on code changes.
• Fail the build if critical use cases fail to ensure quality.

Best Practices for Use Case Testing Framework

1. Write Clear Use Cases: Use simple language describing user goals and steps to avoid confusion.
2. Map Tests to Use Cases: Each automated test should directly reflect a use case scenario.
3. Keep Tests Independent: Tests should not depend on each other to avoid cascading failures.
4. Use Configurations: Separate environment and data settings from test logic for flexibility.
5. Regularly Update Use Cases: Keep use case documents and tests in sync with application changes.

Self Check Question

Where in this folder structure would you add a new automated test script for a use case about "Reset Password"?

Key Result

Organize tests around clear user scenarios with separate use case documents, automated scripts, and flexible configuration.

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