A SUT update changes the UI framework, causing many locators to become unstable. The test automation team wants to minimize future maintenance. What is the best long-term solution?

Use a visual testing tool to avoid locators altogether

Use more robust locators such as data attributes or IDs

Increase the timeout for all tests to handle slow loading

Update the locators in each test script as they fail

A SUT update changes the login button's locator from an ID to a CSS class. The automated test suite uses a page object model. What is the most maintainable way to update the testware?

Add a new page object for the updated login button

Use a CSS selector that matches both the old ID and new class

Update the locator in every test script that clicks the login button

Change the locator in the page object representing the login page

After restructuring the testware for a SUT update, the team runs the regression suite and finds that several tests fail. What should they do first?

Delete the failing tests to make the suite pass

Update the expected results to match the actual results

Analyze the failures to determine if they are due to the SUT update or testware issues

Revert the testware changes to the previous version

A SUT update changes the underlying technology of a web application from Angular to React. The automated test suite uses a custom framework with Angular-specific locators. What is the most appropriate action?

Update the framework's locator strategy to be technology-agnostic

Keep the Angular-specific locators and use a compatibility layer

Switch to a different test automation tool that supports React

Rewrite all test scripts to use React-specific locators

Which of the following is an example of a System Under Test (SUT) update that would necessitate restructuring of the automated testware?

A new feature added to the SUT that introduces additional user workflows

A minor bug fix in the SUT that corrects a calculation error

A change in the SUT's database schema that is transparent to the user interface

A change in the SUT's user interface layout that does not affect the underlying functionality

Certified Tester Advanced Level Test Automation Engineering

Domain 8Objective 3

Objective: Restructure the Automated Testware to Align with System Under Test Updates CTAL-TAE Practice Questions (Page 3)

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

29questions here

6free pages

7concepts

Questions 11–15

11expert · hard
A SUT update changes the UI framework, causing many locators to become unstable. The test automation team wants to minimize future maintenance. What is the best long-term solution?
Select an answer first
12application · medium
A SUT update changes the login button's locator from an ID to a CSS class. The automated test suite uses a page object model. What is the most maintainable way to update the testware?
Select an answer first
13application · medium
After restructuring the testware for a SUT update, the team runs the regression suite and finds that several tests fail. What should they do first?
Select an answer first
14application · medium
A SUT update changes the underlying technology of a web application from Angular to React. The automated test suite uses a custom framework with Angular-specific locators. What is the most appropriate action?
Select an answer first
15foundation · easy
Which of the following is an example of a System Under Test (SUT) update that would necessitate restructuring of the automated testware?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CTAL-TAE

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