A team wants to evaluate whether their test automation is providing value. They currently track the number of automated test cases and the percentage of code coverage. Which additional metric would give the most insight into the effectiveness of the automation in catching regressions?

The number of test automation tools used.

The number of testers on the team.

The total time spent writing automated tests.

The number of defects found by automated tests that would have otherwise reached production.

In an agile team, who is typically responsible for writing and maintaining automated unit tests?

A dedicated test automation specialist only.

The developers, often with support from testers.

What does the metric 'automation execution time' help evaluate?

The efficiency of the test automation suite.

The number of defects in the application.

The skill level of the testers.

When defining a test automation strategy in agile, what is the primary purpose of risk-based prioritization?

To ensure that only low-risk tests are automated.

To automate all tests regardless of risk level.

To focus automation efforts on areas with the highest risk of failure or business impact.

To eliminate the need for manual testing in high-risk areas.

A team developing a web application with a complex user interface and a stable API layer wants to introduce test automation. They have limited time for test maintenance and need fast feedback on every commit. Which approach best aligns with the test automation pyramid and agile principles?

Automate only the end-to-end tests and rely on manual testing for unit and integration levels.

Focus on a broad set of unit and API-level tests, with a small set of end-to-end tests for the most critical journeys.

Create an equal number of unit, integration, and end-to-end tests to ensure balanced coverage across all layers.

Automate a large suite of end-to-end UI tests that cover all critical user journeys, and run them on every commit.

Certified Tester Advanced Level Agile Tester

Domain 6Objective 1

Test Automation in Agile Software Development CTAL-AT Practice Questions (Page 4)

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

38questions here

8free pages

10concepts

Questions 16–20

16application · medium
A team wants to evaluate whether their test automation is providing value. They currently track the number of automated test cases and the percentage of code coverage. Which additional metric would give the most insight into the effectiveness of the automation in catching regressions?
Select an answer first
17foundation · easy
In an agile team, who is typically responsible for writing and maintaining automated unit tests?
Select an answer first
18foundation · easy
What does the metric 'automation execution time' help evaluate?
Select an answer first
19foundation · easy
When defining a test automation strategy in agile, what is the primary purpose of risk-based prioritization?
Select an answer first
20application · medium
A team developing a web application with a complex user interface and a stable API layer wants to introduce test automation. They have limited time for test maintenance and need fast feedback on every commit. Which approach best aligns with the test automation pyramid and agile principles?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CTAL-AT

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