A web application shows a loading spinner that appears and disappears quickly. A test script tries to click a button that is only enabled after the spinner disappears. The script sometimes clicks too early. What is the most reliable approach?

Wait for the button to become enabled using an explicit wait

Click the button multiple times in a loop

Wait for the spinner to disappear using a fixed sleep

An automation script clicks a button that has a dynamically generated ID (e.g., 'btn-12345') that changes on every page load. The script currently fails because it cannot find the element. The button has a stable CSS class 'submit-btn' and is the only button with that class on the page. What is the most robust locator strategy?

Use a CSS selector based on the stable class, e.g., 'button.submit-btn'

Increase the implicit wait timeout before clicking

Use the dynamic ID directly in the locator

Use XPath with the full dynamic ID pattern

What is a key characteristic of a modular test automation framework?

It relies on external data files for all test inputs.

It uses natural language keywords to define test steps.

It uses a single script for the entire application.

It divides the application into modules and creates independent test scripts for each module.

A team uses BDD with Cucumber. They have a feature file with scenarios that are long and contain many implementation details. Business stakeholders find them hard to read. The team wants to improve the readability of the scenarios. What is the best practice?

Remove all scenarios and rely only on step definitions

Rewrite scenarios at a higher level of abstraction, focusing on business value

Combine multiple scenarios into one large scenario

Add more technical details to the scenarios

Why is it important to use synchronization waits in test automation?

To make the test run faster by skipping unnecessary steps.

To verify the correctness of test data.

To handle timing issues where elements are not immediately available due to network latency or dynamic content.

To log the execution time of each test.

Certified Tester Advanced Level Test Automation Engineering

Domain 3Objective 4

Objective: Apply Different Approaches for Automating Test Cases CTAL-TAE Practice Questions (Page 7)

Part of the Domain 3: Test Automation Architecture domain, which makes up ~21% of our current practice bank. ISTQB does not publish an official question count, but from its 90-minute exam (~35–60 total, ~7–13 in this domain), expect 1–3 from this objective — we provide 38 practice questions to prepare you well beyond it. (estimate)

38questions here

8free pages

10concepts

Questions 31–35

31application · medium
A web application shows a loading spinner that appears and disappears quickly. A test script tries to click a button that is only enabled after the spinner disappears. The script sometimes clicks too early. What is the most reliable approach?
Select an answer first
32application · medium
An automation script clicks a button that has a dynamically generated ID (e.g., 'btn-12345') that changes on every page load. The script currently fails because it cannot find the element. The button has a stable CSS class 'submit-btn' and is the only button with that class on the page. What is the most robust locator strategy?
Select an answer first
33foundation · easy
What is a key characteristic of a modular test automation framework?
Select an answer first
34application · medium
A team uses BDD with Cucumber. They have a feature file with scenarios that are long and contain many implementation details. Business stakeholders find them hard to read. The team wants to improve the readability of the scenarios. What is the best practice?
Select an answer first
35foundation · easy
Why is it important to use synchronization waits in test automation?
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.