A tester is reviewing acceptance criteria for a user story about a password reset feature. Which criterion is an example of a POOR acceptance criterion?

The user experience is smooth and seamless.

The user is redirected to the login page after a successful reset.

The system sends a reset link to the user's registered email within 1 minute.

The reset link expires after 30 minutes.

A team is defining acceptance criteria for a user story: 'As a user, I want to search for products by name so that I can find items quickly.' Which set of acceptance criteria is best?

The search works well and is fast.

The search returns results within 2 seconds, shows a message when no matches are found, and allows sorting by price.

The search is user-friendly and intuitive.

The search uses a database index to improve performance.

What is the primary purpose of collaboratively writing user stories with stakeholders?

To replace the need for any further communication during development

To ensure the development team can start coding as soon as possible

To document all technical design decisions before implementation

To capture requirements from multiple perspectives and build a shared understanding

A team is adopting ATDD for a new feature. Which practice best exemplifies ATDD?

Writing a detailed test plan before the sprint starts, but deferring test creation until after coding.

Writing acceptance tests before development begins, based on acceptance criteria.

Writing acceptance tests after the code is complete to verify the feature works.

Writing unit tests before coding, but only for the most critical parts of the feature.

A team is adopting ATDD for a feature that has a high degree of uncertainty. The product owner is concerned that writing acceptance tests upfront may lock in incorrect assumptions. Which approach best addresses this concern while still following ATDD?

Write a minimal set of acceptance tests upfront and refine them as the feature evolves.

Write acceptance tests after development to avoid locking in assumptions.

Write acceptance tests upfront and require the team to follow them strictly without changes.

Write acceptance tests upfront but do not share them with the development team until coding is complete.

Certified Tester Foundation Level

Domain 4Objective 4

Collaborative Testing Practices CTFL Practice Questions (Page 5)

Part of the Domain 4: Test Analysis and Design domain, which makes up ~13% of our current practice bank. ISTQB does not publish an official question count, but from its 60-minute exam (~25–40 total, ~3–5 in this domain), expect 1–1 from this objective — we provide 26 practice questions to prepare you well beyond it. (estimate)

26questions here

6free pages

7concepts

Questions 21–25

21application · medium
A tester is reviewing acceptance criteria for a user story about a password reset feature. Which criterion is an example of a POOR acceptance criterion?
Select an answer first
22application · medium
A team is defining acceptance criteria for a user story: 'As a user, I want to search for products by name so that I can find items quickly.' Which set of acceptance criteria is best?
Select an answer first
23foundation · easy
What is the primary purpose of collaboratively writing user stories with stakeholders?
Select an answer first
24application · medium
A team is adopting ATDD for a new feature. Which practice best exemplifies ATDD?
Select an answer first
25expert · hard
A team is adopting ATDD for a feature that has a high degree of uncertainty. The product owner is concerned that writing acceptance tests upfront may lock in incorrect assumptions. Which approach best addresses this concern while still following ATDD?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CTFL

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. “CTFL” is a trademark of its owner, used for identification only.