Use case testing in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a use case test scenario name.

Testing Fundamentals

use_case_name = "[1]"

Drag options to blanks, or click blank then click option'

ALogin with valid credentials

BCheck input

CTest login

DRun test

Attempts:

3 left

💡 Hint

Common Mistakes

Using vague or generic names like 'Test login' instead of descriptive ones.

The use case test scenario should clearly describe the user action, such as "Login with valid credentials".

2fill in blank

medium

Complete the code to add a step description in the use case test.

Testing Fundamentals

test_steps = ["[1]"]

Drag options to blanks, or click blank then click option'

AEnter username and password

BRun the test

CCheck output

DStart application

Attempts:

3 left

💡 Hint

Common Mistakes

Using generic phrases like 'Run the test' instead of specific user actions.

The test step should describe the user action, such as entering username and password.

3fill in blank

hard

Fix the error in the test case status assignment.

Testing Fundamentals

test_status = "[1]"

Drag options to blanks, or click blank then click option'

Adone

Bpass

Csuccess

Dpassed

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pass' which is a keyword in some languages and not a status string.

The correct status value is usually 'passed' to indicate the test succeeded.

4fill in blank

hard

Fill both blanks to create a dictionary for a use case test step with description and expected result.

Testing Fundamentals

test_step = {"description": "[1]", "expected_result": "[2]"}

Drag options to blanks, or click blank then click option'

AUser enters valid credentials

BSystem displays error message

CUser is logged in successfully

DTest fails

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up the description and expected result values.

The description should state the user action, and the expected result should describe the successful outcome.

5fill in blank

hard

Fill all three blanks to define a use case test dictionary with name, steps, and status.

Testing Fundamentals

use_case_test = {"name": "[1]", "steps": ["[2]"], "status": "[3]"}

Drag options to blanks, or click blank then click option'

AUser resets password

BClicks on reset link

Cpassed

Dfailed

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect status values or mixing step and name values.

The name describes the use case, steps list the user actions, and status shows if the test passed.

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