A user story is: 'As a customer, I want to see my order history so I can track my purchases.' The team is unsure how to test this because the story is incomplete. What technique would best help the team analyze this story?

Create a prototype and ask the customer to confirm it.

Use a requirements workshop to ask clarifying questions and define acceptance criteria together.

Ask the product owner to write a longer story with more details.

Write code based on the story and test it later.

What is the primary purpose of breaking down an epic into smaller user stories?

To reduce the total number of requirements in the backlog

To make the work estimable and deliverable within a single iteration

To combine multiple features into a single deliverable

To eliminate the need for acceptance criteria

A story: 'As a user, I want to filter my transactions by date so I can find specific purchases.' The team needs acceptance criteria. Which set is most testable?

The filter displays all transactions.

The filter works well and shows the right transactions.

The filter is fast and easy to use.

The filter allows selecting a start and end date; results show only transactions within that range; the filter can be cleared with one click.

During a review, the team finds this story: 'As a user, I want to edit my profile so I can update my information.' The team notices that 'edit' is ambiguous. What is the best way to resolve this?

Assume all fields are editable and proceed.

Clarify which fields can be edited (e.g., name, email, phone) and define validation rules in acceptance criteria.

Remove the word 'edit' and just say 'update my profile'.

Split the story into multiple stories for each field.

Which of the following is a sign of ambiguity in a user story?

The use of vague terms like 'quickly' or 'user-friendly'

The story has a clear 'As a... I want... So that...' format

The story includes specific acceptance criteria

The story is small enough to be completed in one iteration

Certified Tester Advanced Level Agile Technical Tester

Domain 1Objective 1

Analyze User Stories and Epics Using Requirements Engineering Techniques CT-ATT Practice Questions (Page 5)

Part of the Requirements Engineering domain, which makes up ~19% of our current practice bank. ISTQB does not publish an official question count, but from its 90-minute exam (~35–60 total, ~7–11 in this domain), expect 4–6 from this objective — we provide 29 practice questions to prepare you well beyond it. (estimate)

29questions here

6free pages

6concepts

Questions 21–25

21application · medium
A user story is: 'As a customer, I want to see my order history so I can track my purchases.' The team is unsure how to test this because the story is incomplete. What technique would best help the team analyze this story?
Select an answer first
22foundation · easy
What is the primary purpose of breaking down an epic into smaller user stories?
Select an answer first
23application · medium
A story: 'As a user, I want to filter my transactions by date so I can find specific purchases.' The team needs acceptance criteria. Which set is most testable?
Select an answer first
24application · medium
During a review, the team finds this story: 'As a user, I want to edit my profile so I can update my information.' The team notices that 'edit' is ambiguous. What is the best way to resolve this?
Select an answer first
25foundation · easy
Which of the following is a sign of ambiguity in a user story?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CT-ATT

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by ISTQB. “CT-ATT” is a trademark of its owner, used for identification only.