Regression-Averse and Test Automation Strategies CTEL-TM-SM Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   Which practice improves the reusability of automated test components?

   • AWriting tests that are tightly coupled to specific data
   • BCopying test code between test cases
   • CCreating page objects or modules that encapsulate UI interactions
   • DEmbedding test data directly in test methods
   Reveal Solution Discussion Select an answer first
2. 7expert · hard

   A company is evaluating whether to automate a set of 500 regression tests. The manual execution takes 10 person-days per cycle, and the team runs the suite monthly. The automation effort is estimated at 100 person-days, with a maintenance cost of 5 person-days per month. The team also needs to purchase a test management tool that integrates with the automation framework, costing $10,000 annually. Which decision is most justified based on ROI analysis?

   • ADo not automate, because the initial investment of 100 person-days is too high compared to the manual effort saved.
   • BAutomate only if the team can reduce the maintenance cost to less than 2 person-days per month, otherwise the ROI is negative.
   • CConduct a full cost-benefit analysis over a 3-year period, including the tool cost, maintenance, and the value of faster feedback and defect detection, before deciding.
   • DAutomate the tests, because the manual effort saved each year (120 person-days) exceeds the maintenance cost (60 person-days) and the initial investment will pay back within two years.
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   A software company's strategic goal is to release new features every two weeks. The test team currently has a large suite of end-to-end automated tests that take 12 hours to run, so they only execute it nightly. The team wants to align their automation strategy with the release cadence. Which change best supports the strategic goal?

   • AReplace all end-to-end tests with unit tests, since unit tests are faster and cheaper to maintain.
   • BShift most test effort to unit and integration tests that run in minutes, and keep a small set of critical end-to-end tests for release validation.
   • CIncrease the number of end-to-end tests to cover all user journeys, and run them in parallel on multiple machines.
   • DContinue with the nightly end-to-end suite, but start it earlier in the evening so results are ready by morning.
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   A team maintains a large automated test suite for a web application. The UI changes frequently, and tests often break because they rely on specific CSS selectors. The team wants to reduce maintenance effort. Which approach best improves maintainability?

   • ARun the tests less frequently, so UI changes accumulate and can be handled in batches.
   • BUse stable attributes like data-testid for element identification, and centralize selectors in a page object model.
   • CReduce the number of UI tests and rely more on manual testing for UI changes.
   • DUpdate the CSS selectors in every test whenever the UI changes, to keep tests in sync.
   Reveal Solution Discussion Select an answer first
6. 10foundation · easy

   What is the purpose of governance in test automation?

   • ATo define rules and guidelines for automation adoption and use
   • BTo eliminate the need for test policies
   • CTo automate all testing activities
   • DTo reduce the number of testers
   Reveal Solution Discussion Select an answer first