User story testing in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a user story format.

Testing Fundamentals

As a [1], I want to [2] so that [3].

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

Auser

Bdeveloper

Ctest

Dmanager

Attempts:

3 left

💡 Hint

Common Mistakes

Using roles like 'developer' or 'manager' instead of 'user'.

Leaving the blank empty.

The user story starts with 'As a user' to specify who benefits from the feature.

2fill in blank

medium

Complete the code to express the goal in a user story.

Testing Fundamentals

As a user, I want to [1] so that I can achieve my goal.

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

Awrite code

Bdeploy software

Cmanage servers

Dlogin to the system

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing developer tasks like 'write code' or 'deploy software'.

Choosing vague or unrelated actions.

The goal should be a user action like 'login to the system' that the user wants to perform.

3fill in blank

hard

Fix the error in the acceptance criteria format.

Testing Fundamentals

Given [1], when I [2], then I should see the [3].

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

Athe server is down

Bthe user clicks logout

Cthe user is logged in

Dthe page crashes

Attempts:

3 left

💡 Hint

Common Mistakes

Using error states like 'server is down' in the 'Given' clause.

Confusing 'Given' with 'When' or 'Then'.

Acceptance criteria start with a condition like 'the user is logged in' to set the context.

4fill in blank

hard

Fill both blanks to complete the acceptance criteria.

Testing Fundamentals

Given [1], when I [2], then I should see a confirmation message.

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

Athe user is logged in

Bthe user clicks submit

Cthe server is down

Dthe user refreshes the page

Attempts:

3 left

💡 Hint

Common Mistakes

Using error states in 'Given'.

Using non-action phrases in 'When'.

The 'Given' clause sets the condition, and the 'When' clause describes the user action triggering the outcome.

5fill in blank

hard

Fill all three blanks to write a complete user story with acceptance criteria.

Testing Fundamentals

As a [1], I want to [2] so that [3].

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

Auser

Breset my password

CI can regain access to my account

Dadmin

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing roles and actions in the wrong places.

Leaving the benefit part empty or unclear.

A complete user story includes the role, the action, and the benefit or reason.

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