Objective: Identify Where Test Automation Produces Unexpected Results CTAL-TAE Practice Questions (Page 3)

Questions 11–15

1. 11application · medium

   A test that verifies a user can log in fails because the login button is not clickable. The test logs show that the page loaded, but the button is disabled. The application logs show that the login service is down. What is the most likely classification of this failure?

   • AAn environmental issue because the login service is unavailable.
   • BAn automation defect because the test did not wait for the button to be enabled.
   • CAn application defect because the login service is down.
   • DA test data issue because the login credentials are invalid.
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   Why is it important to have detailed logging in test automation?

   • ATo make the test execution faster by reducing the need for manual verification
   • BTo provide evidence for test results and support root cause analysis of failures
   • CTo replace the need for a defect tracking system
   • DTo automatically fix defects in the application
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   A test automation suite passes in the staging environment but fails in the production environment. The test verifies that a user can upload a file. The failure is an error message about file size. The staging environment has a file size limit of 10 MB, while production has a limit of 5 MB. What is the most likely cause of the unexpected results?

   • AThe test data file is too large for the production environment's limit.
   • BThe test has a synchronization issue with the file upload.
   • CThe application has a defect in the production build.
   • DThe production environment has a network issue.
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   Which of the following is a recommended approach to avoid synchronization issues in test automation?

   • AIncrease the test's timeout to a very large value
   • BUse fixed sleeps to wait for a predetermined amount of time
   • CIgnore synchronization issues and rely on manual testing
   • DUse explicit waits that wait for a specific condition to be met
   Reveal Solution Discussion Select an answer first
6. 15foundation · easy

   Which of the following best describes a flaky test in test automation?

   • AA test that is not included in the regular regression suite
   • BA test that takes a long time to execute
   • CA test that always fails due to a defect in the application
   • DA test that produces inconsistent results without any changes to the test or application
   Reveal Solution Discussion Select an answer first