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

Questions 21–24

1. 21expert · hard

   A team has a large automated regression suite that runs in 8 hours. The suite is run nightly. A new release introduces a change to the authentication module, which is used by all other modules. The team is considering whether to run the full suite or a subset. The project manager is concerned about the cost of running the full suite every night. What is the best approach?

   • ARun only the tests for the authentication module, since it is the only changed area.
   • BStop running automated tests and rely on manual testing for this release.
   • CRun a subset that covers the authentication module and all dependent modules, and run the full suite only before release.
   • DRun the full suite every night to ensure no regressions are missed.
   Reveal Solution Discussion Select an answer first
2. 22application · medium

   A banking application is about to release a minor update that changes the interest calculation logic for savings accounts. The change is isolated to a single module, but that module is used by several other features. The project has a tight deadline and limited test budget. Which regression testing approach best balances risk and effort?

   • ASkip regression testing because the change is minor and isolated.
   • BRun only the test cases directly related to the interest calculation module.
   • CRun a risk-based subset that includes tests for the changed module and all features that depend on it, prioritizing high-impact areas.
   • DRun the full regression suite to ensure no side effects anywhere.
   Reveal Solution Discussion Select an answer first
4. 23application · medium

   A team has a regression suite with both automated and manual test cases. The automated tests cover the core business logic, while the manual tests cover UI and usability scenarios. For a release that changes the user interface of the checkout process, which test cases should be prioritized for regression?

   • ABoth automated tests for the checkout logic and manual tests for the UI, focusing on the checkout process.
   • BOnly the tests that were previously automated, to save time.
   • CAutomated tests for the checkout logic, since they are faster.
   • DManual tests for the checkout UI, since the change is UI-related.
   Reveal Solution Discussion Select an answer first
5. 24expert · hard

   A product is nearing release with a critical deadline. The regression test budget is fixed and cannot be extended. The team has identified three areas of risk: a high-impact change in the payment module, a medium-impact change in the user profile module, and a low-impact change in the help documentation. The full regression suite would take 10 days, but only 4 days are available. What is the best approach?

   • ARun the full regression suite and accept the schedule delay.
   • BRun a risk-based subset that includes all tests for the payment module, a representative sample for the user profile module, and a minimal check for the help documentation.
   • CRun only the tests for the payment module, as it has the highest impact.
   • DRun only the automated tests, since they are faster, and skip manual tests.
   Reveal Solution Discussion Select an answer first