CTFL-v4 Test Tools Practice Question
A test team has adopted a test automation tool for a web application. After several sprints, they notice that the automated test suites are producing many false failures due to frequent changes in the user interface. Which approach best addresses this problem while maintaining the benefits of test automation?
⚠ Common exam trap
The trap here is assuming that more test cases or different tools will solve the problem, rather than addressing the design flaw of coupling test logic directly to UI locators.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Implement a page object model to separate test logic from UI locators.
The core issue is that UI changes cause automation scripts to fail even when the application behaves correctly. A page object model abstracts UI element locators into separate classes, so changes to the UI require updates in only one place, not across all tests. This reduces maintenance effort and false failures, preserving the value of automation. Other options either increase fragility or reduce test frequency without addressing the root cause.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Switch to a capture/playback tool to record tests directly from user interactions.
Why it's wrong here
Capture/playback tools record hard-coded scripts that are even more sensitive to UI changes, as any alteration in element position or identifier breaks the recorded sequence. This would worsen the false failure problem, not alleviate it, because the scripts lack abstraction and require re-recording for even minor UI updates.
- ✗
Reduce the frequency of test execution to once per release.
Why it's wrong here
Running tests less often does not fix the false failures; it merely delays their detection and reduces the feedback loop's value. The underlying brittleness remains, and when tests do run, they will still fail falsely. This approach sacrifices the benefits of continuous feedback and early defect detection that test automation provides.
- ✓
Implement a page object model to separate test logic from UI locators.
Why this is correct
A page object model encapsulates UI element locators and interactions into reusable classes, so when the UI changes, only the page object needs updating rather than every test that uses those elements. This reduces duplication and makes the suite more maintainable and resilient to UI changes, directly addressing the false failures caused by frequent UI modifications.
- ✗
Increase the number of test cases in the automated suite to cover more UI variations.
Why it's wrong here
Adding more test cases would likely increase the number of false failures because the root cause is the brittleness of the automation scripts against UI changes, not insufficient coverage. More scripts would simply replicate the same fragility, leading to higher maintenance costs and reduced trust in the test results, without solving the underlying issue.
About these practice questions
This CTFL-v4 question is part of Courseiva's 144-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official ISTQB exam blueprint
This CTFL-v4 practice question is part of Courseiva's free ISTQB certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CTFL-v4 exam.