A team is using test automation to support continuous delivery. They want to measure whether the automation is actually reducing the time to release and improving quality. Which combination of metrics would give the most balanced view?

Number of automated tests and percentage of code coverage.

Number of testers and number of developers on the team.

Test execution time and number of flaky tests.

Cycle time from commit to deployment and defect escape rate.

A team's CI pipeline includes automated tests, but the pipeline often fails due to environment issues, such as missing services or unstable test data. Developers have started to ignore the pipeline results because they are frequently false alarms. What is the most effective way to restore trust in the CI pipeline?

Stabilize the test environment by using containerization or infrastructure as code, and fix test data management.

Remove the automated tests from the pipeline and run them manually before release.

Increase the number of test runs to see if the environment issues are consistent.

Make the pipeline less strict by allowing failures to be overridden by developers.

A team wants to automate performance testing in their CI pipeline, but they are concerned about the cost and time of running full load tests on every commit. They also need to ensure that performance regressions are caught early. Which approach best balances these concerns?

Run full load tests on every commit to catch all performance issues immediately.

Run performance tests only in the staging environment after deployment.

Skip performance testing in CI and rely on manual performance testing before release.

Run a small set of performance smoke tests on every commit and full load tests on a nightly or pre-release basis.

A team's CI pipeline currently runs all automated tests sequentially, taking over an hour. Developers complain that they get feedback too late to fix issues while context is fresh. Which change would most effectively improve feedback speed without sacrificing reliability?

Split the test suite into fast and slow groups; run fast tests on every commit and slow tests on a scheduled basis or on merge.

Increase the number of parallel CI agents so all tests run concurrently, regardless of dependencies.

Move all automated tests to a separate environment that runs only after the code is deployed to production.

Run the full test suite only on nightly builds and rely on code reviews for immediate feedback.

Certified Tester Advanced Level Agile Tester

Domain 6Objective 1

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

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 21–25

21expert · hard
A team is using test automation to support continuous delivery. They want to measure whether the automation is actually reducing the time to release and improving quality. Which combination of metrics would give the most balanced view?
Select an answer first
22expert · hard
A team's CI pipeline includes automated tests, but the pipeline often fails due to environment issues, such as missing services or unstable test data. Developers have started to ignore the pipeline results because they are frequently false alarms. What is the most effective way to restore trust in the CI pipeline?
Select an answer first
23foundation · easy
According to the test automation pyramid, which type of tests should form the largest base of the pyramid?
Select an answer first
24expert · hard
A team wants to automate performance testing in their CI pipeline, but they are concerned about the cost and time of running full load tests on every commit. They also need to ensure that performance regressions are caught early. Which approach best balances these concerns?
Select an answer first
25application · medium
A team's CI pipeline currently runs all automated tests sequentially, taking over an hour. Developers complain that they get feedback too late to fix issues while context is fresh. Which change would most effectively improve feedback speed without sacrificing reliability?
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.

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

Questions 21–25

A team is using test automation to support continuous delivery. They want to measure whether the automation is actually reducing the time to release and improving quality. Which combination of metrics would give the most balanced view?

According to the test automation pyramid, which type of tests should form the largest base of the pyramid?

A team wants to automate performance testing in their CI pipeline, but they are concerned about the cost and time of running full load tests on every commit. They also need to ensure that performance regressions are caught early. Which approach best balances these concerns?

A team's CI pipeline currently runs all automated tests sequentially, taking over an hour. Developers complain that they get feedback too late to fix issues while context is fresh. Which change would most effectively improve feedback speed without sacrificing reliability?

Keep studying — Test Automation and Test Tools