Objective: Test Automation Solution Maintainability CTAL-TAE Practice Questions (Page 1)

Questions 1–5

1. 1application · medium

   A test automation team wants to use a maintainability metric to predict which parts of their test code are most likely to require frequent changes in the future. They have historical data on how often each module has been modified. Which metric would be most predictive of future maintenance effort?

   • ACode churn, measured as the number of lines changed per module over time
   • BThe average execution time of tests in each module
   • CThe number of comments in each module
   • DThe number of test cases that call each module
   Reveal Solution Discussion Select an answer first
2. 2application · medium

   A test automation team is struggling with flaky tests that fail intermittently due to timing issues. They want to improve the maintainability of their tests by making them more reliable. Which technique would be most effective?

   • AIncrease the default timeout for all findElement calls to a very high value.
   • BRemove all timing-related assertions from the tests to avoid failures.
   • CImplement explicit waits that wait for specific conditions, such as element visibility or enabled state, instead of fixed sleeps.
   • DRetry each test automatically up to three times before reporting a failure.
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   Which design guideline helps isolate the impact of changes to the system under test on the test automation?

   • AWriting tests that directly interact with the database
   • BUsing page object model or similar abstraction layers
   • CHard-coding element locators in every test
   • DUsing global variables for all test data
   Reveal Solution Discussion Select an answer first
5. 4foundation · easy

   Which guideline is most effective for designing maintainable test automation?

   • AAvoid comments because they become outdated
   • BUse descriptive names for test methods and variables
   • CWrite long test scripts that cover multiple scenarios
   • DEmbed test data directly within each test script
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   A test automation team is refactoring a suite of end-to-end tests. They notice that many tests repeat the same setup steps, such as creating a user account and configuring permissions. They want to reduce duplication and make the tests easier to maintain. Which technique would best achieve this?

   • AExtract the common setup steps into a reusable helper function and call it from each test that needs it.
   • BIncrease the number of assertions in each test to ensure the setup steps are thoroughly verified.
   • CCopy the setup steps into each test method so that every test is self-contained and independent.
   • DDisable the tests that require complex setup to reduce the maintenance burden.
   Reveal Solution Discussion Select an answer first