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

Questions 6–10

1. 6foundation · easy

   When deciding which test cases to include in a regression suite, which factor should be considered?

   • AThe programming language used to write the test case.
   • BThe risk and impact of the functionality covered by the test case.
   • CThe number of test cases already in the suite.
   • DThe name of the test case.
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   What is a common approach to handling flaky automated tests?

   • AIgnore the failures and assume the test is not important.
   • BRun the test only once to avoid flakiness.
   • CDelete the test immediately to avoid false failures.
   • DInvestigate the root cause and fix the test or the underlying issue.
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   Which of the following is a criterion for selecting test cases to include in a regression test suite?

   • ATest cases that have never failed before.
   • BTest cases that are the fastest to execute.
   • CTest cases that are the easiest to automate.
   • DTest cases that cover functionality that has been changed or is likely to be affected by changes.
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   A team wants to reduce the time between code changes and the detection of regressions. They currently run regression tests manually at the end of each sprint. What practice should they adopt?

   • AIncrease the number of manual testers to run regression tests more frequently.
   • BRun a subset of automated regression tests in a continuous integration pipeline on every commit.
   • CRun the full regression suite only when the release candidate is ready.
   • DDelay regression testing until the end of the sprint to allow more time for feature development.
   Reveal Solution Discussion Select an answer first
6. 10expert · hard

   A team has a limited regression testing budget for the upcoming sprint. They have identified the following changes: a new feature in the checkout process (high impact, high likelihood of regression), a minor update to the search filter (low impact, low likelihood), and a refactoring of the database access layer (medium impact, high likelihood). How should they allocate their testing effort?

   • ATest the search filter and database layer, and skip the checkout process.
   • BTest only the checkout process, since it has the highest impact.
   • CTest the checkout process and database layer thoroughly, and run a smoke test on the search filter.
   • DTest all three changes equally to ensure balanced coverage.
   Reveal Solution Discussion Select an answer first