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.