What is a common drawback of automating at the system (end-to-end) level?

Tests are often slow and brittle, making them expensive to maintain

They cannot be executed in a CI/CD pipeline

They require no test data setup

They provide no coverage of business workflows

A team is automating tests for a system that integrates with several third-party services. The third-party services are sometimes unavailable and have rate limits. The team wants to run tests frequently in CI. What is the most effective way to handle these dependencies in the automation suite?

Run all tests against the real third-party services to ensure accuracy

Mock all third-party services in all tests, including integration tests

Skip tests that involve third-party services

Use test doubles (mocks/stubs) for third-party services in most tests, and run a small set of integration tests against the real services less frequently

An Agile team is building a web application with a complex user interface. They currently have a large number of UI end-to-end tests that run slowly and are flaky. They want to adopt the test automation pyramid to improve reliability and speed. What should be their primary strategy?

Increase the number of UI end-to-end tests to cover more user journeys

Replace all automated tests with manual exploratory testing

Move all tests to the system level to test the complete application as a black box

Shift most test effort to unit and integration tests, keeping a small set of end-to-end tests for critical journeys

Which of the following is a key benefit of automating unit tests?

They are the cheapest tests to maintain over time

They eliminate the need for any manual testing

They provide fast feedback to developers on code changes

They validate the system from the user's perspective

Certified Tester Advanced Level Agile Technical Tester

Domain 3Objective 2

Level of Automation CT-ATT Practice Questions (Page 2)

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

21questions here

5free pages

4concepts

Questions 6–10

6foundation · easy
According to the test automation pyramid, which level should have the largest number of automated tests?
Select an answer first
7foundation · easy
What is a common drawback of automating at the system (end-to-end) level?
Select an answer first
8expert · hard
A team is automating tests for a system that integrates with several third-party services. The third-party services are sometimes unavailable and have rate limits. The team wants to run tests frequently in CI. What is the most effective way to handle these dependencies in the automation suite?
Select an answer first
9application · medium
An Agile team is building a web application with a complex user interface. They currently have a large number of UI end-to-end tests that run slowly and are flaky. They want to adopt the test automation pyramid to improve reliability and speed. What should be their primary strategy?
Select an answer first
10foundation · easy
Which of the following is a key benefit of automating unit tests?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CT-ATT

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