Which of the following is an example of adapting a regression test strategy?

Increasing the frequency of regression testing without reviewing the test suite.

Adding new test cases for recently added features and removing obsolete ones.

Keeping the same test suite throughout the project to ensure consistency.

Running the same set of tests regardless of changes.

What is a primary reason for updating automated test cases in an agile project?

To reduce the time needed to execute the test suite.

To align them with the latest changes in requirements and code.

To increase the number of test cases in the regression suite.

To ensure that all test cases are automated.

An agile team has a large legacy module that is rarely changed but is critical to the product. They are introducing a new feature that touches a small part of that module. The team wants to manage regression risk without slowing down the current sprint. What is the most effective approach?

Run a focused set of manual regression tests on the affected areas and add automated tests for the new feature.

Skip regression testing for the legacy module since it is rarely changed and rely on the new feature's automated tests.

Automate all existing manual regression tests for the legacy module before the new feature is developed.

Replace all manual tests with automated tests for the entire application to ensure continuous regression coverage.

What is a key strength of manual regression testing compared to automated regression testing?

It is faster to execute than automated tests.

It can adapt to unexpected situations and explore the application creatively.

It is more reliable than automated tests.

It requires no test design effort.

A team has been running the same regression suite for several releases. They notice that the suite takes too long to execute and that some tests rarely fail. They want to optimize the suite without increasing regression risk. What should they do?

Increase the frequency of running the suite to catch regressions earlier.

Analyze the risk and value of each test and remove or relegate low-value tests to a separate, less frequent suite.

Run the entire suite in parallel to reduce execution time.

Remove all tests that have not failed in the last six months.

Certified Tester Foundation Level Agile Tester

Domain 2Objective 7

Managing Regression Risk with Evolving Manual and Automated Test Cases CT-AT Practice Questions (Page 4)

Part of the Fundamental Agile Testing Principles, Practices, and Processes domain, which makes up ~44% of our current practice bank.

32questions here

7free pages

9concepts

Questions 16–20

16foundation · easy
Which of the following is an example of adapting a regression test strategy?
Select an answer first
17foundation · easy
What is a primary reason for updating automated test cases in an agile project?
Select an answer first
18application · medium
An agile team has a large legacy module that is rarely changed but is critical to the product. They are introducing a new feature that touches a small part of that module. The team wants to manage regression risk without slowing down the current sprint. What is the most effective approach?
Select an answer first
19foundation · easy
What is a key strength of manual regression testing compared to automated regression testing?
Select an answer first
20expert · hard
A team has been running the same regression suite for several releases. They notice that the suite takes too long to execute and that some tests rarely fail. They want to optimize the suite without increasing regression risk. What should they do?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CT-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. “CT-AT” is a trademark of its owner, used for identification only.