A company has a nightly regression suite at the system level that takes 6 hours to run. They are introducing component-level automation and want to provide faster feedback to developers. What is the best strategy?

Run both component and system-level tests on every commit to maximize coverage.

Run the system-level regression suite on every commit and remove component tests to avoid duplication.

Replace the system-level regression suite with the component tests to reduce execution time.

Run component tests on every code commit and keep the system-level regression suite on a nightly schedule.

A team is transitioning from manual to automated testing. They have existing manual test cases at the system level. They want to automate them and also create automated component and integration tests. They have limited resources and need to prioritize. What is the best approach?

Start by automating the component and integration tests, and gradually automate the system-level tests based on risk and value.

Automate all test levels at the same time to get full coverage quickly.

Automate all system-level tests first, since they cover the most.

Automate only the component tests and keep the rest manual.

What is a key benefit of producing integrated reports from test automation across test levels?

They automatically fix any failing tests

They guarantee that all defects are found

They provide a holistic view of the quality of the system under test

They eliminate the need for manual test reporting

During a project, the integration test team needs to know which component versions were used in the latest system build to reproduce a defect. What artifact should the component test level provide to support this?

A build manifest listing component versions and their test results.

A summary of all test cases executed at the component level.

A copy of the component test scripts.

A list of defects found during component testing.

Which of the following is a common challenge when integrating test automation across test levels?

Deciding which test cases to automate first

Ensuring that test data is consistent and available across all levels

Choosing the right programming language for the automation framework

Having too many test cases to execute manually

Certified Tester Test Automation Strategy

Domain 3Objective 1

Integration Across Test Levels CT-TAS Practice Questions (Page 2)

Part of the Domain 3: Preparing for Test Automation domain, which makes up ~16% of our current practice bank. ISTQB does not publish an official question count, but from its 60-minute exam (~25–40 total, ~4–6 in this domain), expect 1–2 from this objective — we provide 25 practice questions to prepare you well beyond it. (estimate)

25questions here

5free pages

6concepts

Questions 6–10

6application · medium
A company has a nightly regression suite at the system level that takes 6 hours to run. They are introducing component-level automation and want to provide faster feedback to developers. What is the best strategy?
Select an answer first
7expert · hard
A team is transitioning from manual to automated testing. They have existing manual test cases at the system level. They want to automate them and also create automated component and integration tests. They have limited resources and need to prioritize. What is the best approach?
Select an answer first
8foundation · easy
What is a key benefit of producing integrated reports from test automation across test levels?
Select an answer first
9application · medium
During a project, the integration test team needs to know which component versions were used in the latest system build to reproduce a defect. What artifact should the component test level provide to support this?
Select an answer first
10foundation · easy
Which of the following is a common challenge when integrating test automation across test levels?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CT-TAS

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