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

Questions 26–30

1. 26application · medium

   A team wants to ensure that regression tests are run automatically whenever code is integrated. They are using a CI server. What is the best practice for configuring the regression tests?

   • ARun regression tests only when a release candidate is created.
   • BRun a fast subset of regression tests on every commit and the full suite on a nightly or scheduled basis.
   • CRun regression tests manually after each sprint.
   • DRun the full regression suite on every commit to catch regressions early.
   Reveal Solution Discussion Select an answer first
2. 27foundation · easy

   What is the primary definition of regression risk in the context of agile software development?

   • AThe risk that the test environment will not be available when needed for testing.
   • BThe possibility that a change to the software will introduce defects into existing, previously working functionality.
   • CThe risk that the development team will not complete all planned features by the release date.
   • DThe risk that the software will not meet the performance requirements specified by the customer.
   Reveal Solution Discussion Select an answer first
4. 28expert · hard

   A team is planning the regression test suite for the next sprint. The product owner has identified two high-risk areas: the payment processing module (frequently changed, high business impact) and the reporting module (rarely changed, low business impact). The team has limited testing capacity. What should they do?

   • AFocus most testing effort on the payment module and run only smoke tests on the reporting module.
   • BTest only the payment module thoroughly and skip the reporting module entirely.
   • CAllocate equal testing effort to both modules to ensure balanced coverage.
   • DAutomate all tests for both modules to maximize coverage.
   Reveal Solution Discussion Select an answer first
5. 29application · medium

   A team is developing a web application with frequent releases. They have noticed that regressions are sometimes introduced in areas that were not directly changed. What is the most effective way to manage this risk?

   • AImplement a comprehensive automated regression suite that runs in CI.
   • BLimit the number of changes in each release to reduce the chance of regressions.
   • CRely on manual testing by the development team before each release.
   • DIncrease the frequency of releases to reduce the time between changes.
   Reveal Solution Discussion Select an answer first
6. 30foundation · easy

   How do test cases typically evolve in an agile project?

   • AThey are created once at the start of the project and remain unchanged until release.
   • BThey are replaced entirely by automated test cases after the first iteration.
   • CThey are only updated when a defect is found in production.
   • DThey are updated to reflect new requirements, changed behavior, and lessons learned from defects.
   Reveal Solution Discussion Select an answer first