Objective: Test Automation Development CTAL-TAE Practice Questions (Page 3)

Questions 11–15

1. 11expert · hard

   A company's CI pipeline runs a large test suite on every commit. The suite takes 2 hours and often fails due to environment issues, not application defects. The team wants to reduce false failures and improve pipeline efficiency. They are considering running the suite on a schedule instead of on every commit. Which approach best addresses the root cause while maintaining quality?

   • ARun the suite nightly and only run a smoke test on every commit
   • BRun the suite on a schedule and ignore failures that are not reproducible
   • CKeep running on every commit but improve environment stability and add retry logic for known transient failures
   • DMove the suite to a separate, more stable environment and run it only on merge requests
   Reveal Solution Discussion Select an answer first
2. 12expert · hard

   A test suite for a web application occasionally fails because a pop-up dialog appears unexpectedly and blocks interaction with the page. The team wants to handle this robustly without masking real defects. Which error handling strategy is most appropriate?

   • AIncrease the timeout to allow the pop-up to disappear on its own
   • BFail the test immediately when a pop-up is detected
   • CAdd a check for the pop-up before each interaction and dismiss it if present, then log a warning
   • DUse a global exception handler that dismisses any pop-up and continues the test
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   A team is automating tests for a CRM application. They need to run tests in parallel across multiple environments (staging and QA) and ensure that each test run has isolated, consistent data. The application's database is shared and tests often modify records. Which test data management strategy best supports reliable parallel execution?

   • ACreate a unique dataset for each test run using API calls to set up and tear down data
   • BRestore a database backup before each test suite runs
   • CUse a shared, static dataset that is read-only for all tests
   • DHave each test generate its own data and leave it in the database
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   A test automation team is setting up reporting for their CI pipeline. They need to quickly identify which test failed, why it failed, and what the application state was at the time of failure. Which reporting and logging approach best supports this requirement?

   • ALog only the final pass/fail status of each test
   • BCapture a screenshot and HTML page source on every test failure
   • CSend an email notification with the test summary to the team
   • DLog all WebDriver commands and responses for every test
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   A team's UI test suite has become flaky, with tests failing intermittently due to timing issues and changes in the application's dynamic content. The team wants to reduce flakiness and improve maintainability. Which approach is most effective?

   • ARemove the tests that are flaky from the suite
   • BRun the suite multiple times and only report failures that occur consistently
   • CUse explicit waits that target the specific conditions of the dynamic elements
   • DIncrease the default timeout for all WebDriver waits
   Reveal Solution Discussion Select an answer first