Which factor is most likely to influence the extent of regression testing needed for a release?

The risk of changes breaking existing functionality

The size of the regression test suite

The type of test management tool used

The number of testers available on the team

What is the primary purpose of defining the scope of regression testing for a new release?

To test only the new features added in the release

To validate that the system is ready for production deployment

To ensure the system meets all performance requirements

To verify that all existing functionality still works after changes are made

A team is preparing for a release that includes a fix to the login module and a new feature that adds a 'remember me' option. The login module is used by all other modules. Which set of regression tests should be selected?

All tests from the previous release, regardless of relevance to the changes.

Only the tests that failed in the previous release, assuming they are the most likely to regress.

Only the tests for the new 'remember me' feature, since the login fix is minor.

All tests that cover the login module and the new 'remember me' feature, plus a sample of tests from other modules that use login.

A team is planning regression testing for a release that includes a change to the shipping calculation logic. The change is intended to fix a defect that caused incorrect shipping costs for international orders. The team has limited time and budget. Which regression testing approach is most appropriate?

Run only the tests for international shipping, since the defect was specific to that area.

Run the full regression suite to ensure no side effects anywhere.

Run only the tests that failed for the original defect, to verify the fix.

Run all tests related to shipping, including international and domestic, plus a sample of tests for order processing and payment.

In risk-based regression testing, which existing functionality should be given the highest priority for inclusion in the regression test suite?

Functionality that is simple and has never failed before

Functionality that is rarely used but easy to test

Functionality that is complex and frequently used by users

Functionality that was recently added and is well-tested

Certified Tester Advanced Level Test Analyst

Domain 2Objective 2

Determining the Scope of Regression Testing CTAL-TA Practice Questions (Page 4)

Part of the The Tasks of the Test Analyst in Risk-Based Testing domain, which makes up ~12% of our current practice bank. ISTQB does not publish an official question count, but from its 120-minute exam (~50–80 total, ~6–10 in this domain), expect 3–5 from this objective — we provide 24 practice questions to prepare you well beyond it. (estimate)

24questions here

5free pages

6concepts

Questions 16–20

16foundation · easy
Which factor is most likely to influence the extent of regression testing needed for a release?
Select an answer first
17foundation · easy
What is the primary purpose of defining the scope of regression testing for a new release?
Select an answer first
18application · medium
A team is preparing for a release that includes a fix to the login module and a new feature that adds a 'remember me' option. The login module is used by all other modules. Which set of regression tests should be selected?
Select an answer first
19expert · hard
A team is planning regression testing for a release that includes a change to the shipping calculation logic. The change is intended to fix a defect that caused incorrect shipping costs for international orders. The team has limited time and budget. Which regression testing approach is most appropriate?
Select an answer first
20foundation · easy
In risk-based regression testing, which existing functionality should be given the highest priority for inclusion in the regression test suite?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CTAL-TA

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