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.