User story testing in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding User Story Acceptance Criteria

Which of the following best describes the purpose of acceptance criteria in user story testing?

A They describe the user interface design details for the user story.

B They list all the technical tasks developers must perform to implement the user story.

C They define the conditions that must be met for the user story to be considered complete and working as expected.

D They specify the project deadlines and resource allocation for the user story.

💡 Hint

Think about what helps testers decide if a user story is done.

Acceptance criteria are clear, testable conditions that define when a user story is complete and meets the user's needs.

❓ assertion

intermediate

Writing Assertions for User Story Testing

You have a user story: "As a user, I want to log in with valid credentials so that I can access my dashboard." Which assertion best tests this story?

A Assert that the login function returns a success message when given valid username and password.

B Assert that the login page loads within 5 seconds.

C Assert that the logout button is visible after login.

D Assert that the password field accepts only numbers.

💡 Hint

Focus on what the user story wants to achieve.

The user story is about logging in with valid credentials, so the assertion should check if login succeeds with correct inputs.

❓ Predict Output

advanced

Test Result from User Story Scenario

Given this test code for a user story about adding items to a cart, what is the test result?

Testing Fundamentals

def test_add_item_to_cart():
    cart = []
    def add_item(item):
        if item != '':
            cart.append(item)
    add_item('apple')
    add_item('')
    assert len(cart) == 1
    assert cart[0] == 'apple'
    return 'pass'

result = test_add_item_to_cart()

A "pass"

B AssertionError

C TypeError

D IndexError

💡 Hint

Check what items are added to the cart and what the assertions check.

The function adds 'apple' and ignores empty string. The assertions check cart length is 1 and first item is 'apple', so test passes.

🔧 Debug

advanced

Debugging a Failing User Story Test

Consider this test for a user story: "As a user, I want to reset my password." The test fails with an AssertionError. What is the likely cause?

Testing Fundamentals

def test_password_reset():
    user = {'email': '[e-mail]', 'password': 'oldpass'}
    def reset_password(email, new_pass):
        if email == user['email']:
            user['password'] = new_pass
    reset_password('[e-mail]', 'newpass')
    assert user['password'] == 'oldpass'

A The user dictionary is missing the password key.

B The assertion expects the old password but the password was changed to 'newpass'.

C The email check in reset_password is incorrect.

D The reset_password function does not update the password correctly.

💡 Hint

Look at what the assertion expects versus what the function does.

The function changes the password to 'newpass', but the assertion expects it to remain 'oldpass', causing failure.

❓ framework

expert

Choosing the Best Test Framework for User Story Automation

You want to automate acceptance tests for user stories that involve web UI interactions and API calls. Which test framework setup is best suited?

A Use a simple script with print statements to manually verify UI and API responses.

B Use a unit testing framework like JUnit only for backend API testing without UI automation.

C Use a load testing tool like JMeter to test user story acceptance criteria.

D Use a BDD framework like Cucumber with Selenium for UI and REST-assured for API testing, integrating tests with user story descriptions.

💡 Hint

Think about tools that connect user stories with automated acceptance tests for UI and APIs.

BDD frameworks like Cucumber allow writing tests in user story language, Selenium automates UI, and REST-assured handles API calls, making this setup ideal.

Practice

1. What is the main purpose of user story testing in software development?

easy

A. To verify that the software meets the user's needs and expectations

B. To check the software's installation process

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

D. To review the software's code quality

Solution

1. Step 1: Understand user story testing focus

   User story testing focuses on validating features from the user's perspective, ensuring the software solves real user problems.

2. Step 2: Compare options to user story testing goal

   Options A, B, and D focus on technical or internal aspects, not user needs.

3. Final Answer:

   To verify that the software meets the user's needs and expectations -> Option A

4. Quick Check:

   User needs = Verify software meets needs [OK]

Hint: User story testing checks if software fits user needs [OK]

Common Mistakes:

• Confusing user story testing with performance testing
• Thinking it focuses on code quality
• Assuming it tests installation or setup

2. Which of the following is the correct way to write a test scenario from a user story: "As a user, I want to log in so that I can access my dashboard"?

easy

A. Test if the login page loads within 5 seconds

B. Check if the database connection is active

C. Verify that entering valid credentials allows access to the dashboard

D. Measure the CPU usage during login

Solution

1. Step 1: Identify the user story goal

   The story is about logging in to access the dashboard, so the test should check login success with valid credentials.

2. Step 2: Match test scenarios to the story

   Verify that entering valid credentials allows access to the dashboard directly tests the login functionality as per the story. Options A, C, and D focus on performance or backend, not user goal.

3. Final Answer:

   Verify that entering valid credentials allows access to the dashboard -> Option C

4. Quick Check:

   Test scenario matches user goal [OK]

Hint: Test scenarios must match user story goals exactly [OK]

Common Mistakes:

• Testing technical details unrelated to user goal
• Confusing performance tests with functional tests
• Ignoring the 'so that' part of the user story

3. Given the user story: "As a shopper, I want to add items to my cart so that I can buy them later", which test result indicates the feature works correctly?

medium

A. After adding an item, the cart shows the correct item and quantity

B. The website loads the homepage in under 2 seconds

C. The user receives an error when trying to add an item

D. The cart icon disappears after adding an item

Solution

1. Step 1: Understand the user story's expected outcome

   The story expects items to be added to the cart and visible for later purchase.

2. Step 2: Identify the test result that matches this outcome

   After adding an item, the cart shows the correct item and quantity confirms the cart updates correctly. Options A, B, and C do not confirm correct cart behavior.

3. Final Answer:

   After adding an item, the cart shows the correct item and quantity -> Option A

4. Quick Check:

   Cart updates correctly = Feature works [OK]

Hint: Look for test results that confirm user story success [OK]

Common Mistakes:

• Confusing performance with functional correctness
• Assuming errors mean success
• Ignoring UI feedback like cart icon visibility

4. A tester wrote this test step for the user story "As an admin, I want to delete users": "Click the delete button and check if the user is removed". The test fails because the user is not deleted. What is the most likely error?

medium

A. The delete button was clicked twice accidentally

B. The test missed confirming the confirmation popup before deletion

C. The user was deleted but the page did not refresh

D. The test used the wrong user credentials

Solution

1. Step 1: Analyze the test step and failure

   The test clicks delete but the user remains, suggesting a missing confirmation step.

2. Step 2: Identify common deletion flow issues

   Many delete actions require confirming a popup; missing this blocks deletion. Options B, C, and D are less likely causes.

3. Final Answer:

   The test missed confirming the confirmation popup before deletion -> Option B

4. Quick Check:

   Missing confirmation popup blocks deletion [OK]

Hint: Check for confirmation dialogs in delete actions [OK]

Common Mistakes:

• Ignoring confirmation popups
• Assuming UI refresh means deletion
• Not verifying correct user permissions

5. You have this user story: "As a user, I want to filter products by price so that I can find affordable options." Which of the following test cases best covers this story including edge cases?

hard

A. Test filtering with negative price values

B. Test filtering with only maximum price set to 100

C. Test filtering with price range 50 to 50

D. Test filtering with minimum price 0, maximum price 100, and no products in range

Solution

1. Step 1: Understand the user story and edge cases

   The story requires filtering by price, including cases where no products match.

2. Step 2: Evaluate test cases for coverage

   Test filtering with minimum price 0, maximum price 100, and no products in range tests a full range including zero and no matching products, covering normal and edge cases. Options B, C, and D miss some edge cases or use invalid inputs.

3. Final Answer:

   Test filtering with minimum price 0, maximum price 100, and no products in range -> Option D

4. Quick Check:

   Full range and no-match edge case tested [OK]

Hint: Include edge cases like empty results in user story tests [OK]

Common Mistakes:

• Ignoring no-match scenarios
• Testing only partial filters
• Using invalid negative prices without story support