Free CT-TAE – Certified Tester Test Automation Engineer Practice Test Question

Select an option, then click Submit answer.

• ○

  The TAS must run in the development environment because development and programming knowledge are required for its maintainability

• ○

  The TAS must be under configuration management, along with the test suite, the testware artefacts and the test environment in which it runs

• ○

  The TAS must separate the test scripts from the environment in which it runs and from the associated harnesses and artefacts

• ○

  The TAS must consist of components that can be easily replaced without affecting the overall behavior of the TAS itself
  
  

Select an option, then click Submit answer.

• ○

  Remove the intermittently failing test from the test suite and investigate the reason why the test sometimes passes and sometimes fails.

• ○

  Check that the production defect that was reported was an actual defect

• ○

  Run the automated test suite again and if the test now passes - do nothing

• ○

  Reference: https://www.researchgate.net/publication/341396240_Intermittently_Failing_Tests_in_the_Embedded_Systems_Domain

Select an option, then click Submit answer.

• ○

  Perform an analysis of risks versus benefits for the enhanced TAS and then decide which version to use.

• ○

  Use the previous version because this was proven to work. It will be too risky to use the new version, with unresolved issues, for a live system.

• ○

  Use the new version because, despite some issues, it works, and the live system should not be tested using a different TAS.

• ○

  Use the new version of the TAS for the first maintenance release on a trial basis. If issues are encountered, switch to the previous version for later releases until the issues are resolved.

Select an option, then click Submit answer.

• ○

  Move to a model-based approach to scripting where the models include the keywords.

• ○

  Do nothing, each team are working in isolation and they are all experiencing significant benefits in the way they are currently working.

• ○

  Provide each team with a set of guidelines and naming conventions for keywords.

• ○

  Create a central library of keywords and associated definitions for each team to use.

Select an option, then click Submit answer.

• ○

  Test automation cannot measure code coverage for the SUT, only the code for the automation tools and scripts. The automated test cases would need to be run manually with a code coverage and reporting tool running in the background.

• ○

  The automated testware would record overall code coverage for each run and add the figure to a new row in a pre-formatted Excel spreadsheet. You would then present the spreadsheet to stakeholders so they could look for changes in coverage.

• ○

  The automated testware would record overall code coverage for each run, export the data to a pre-formatted Excel spreadsheet that automatically updates a trend analysis bar chart for you to distribute to stakeholders.

• ○

  The automated testware would record the pass/fail rate of each regression test case, export the data to a pre-formatted Excel spreadsheet that automatically updates a trend analysis success rate bar chart and emails it to stakeholders.

Select an option, then click Submit answer.

• ○

  The average maintenance cost to keep an automated test in sync with the SUT

• ○

  The number of hours of manual test effort saved by implementing a TAS

• ○

  A measure of defect density within the TAS automation code

• ○

  A measure of how many automated tests pass and fail

Select an option, then click Submit answer.

• ○

  The connectivity from the TAS to the dedicated test interfaces will not work

• ○

  The process of configuring the TAS will be error-phone due to manual intervention

• ○

  The automated test cases will not contain the expected result

• ○

  False alarms, that are unlikely to occur in the real world, will be observed during testing
  

Select an option, then click Submit answer.

• ○

  Run the regression suite as planned and see If the tests fail again if they do, determine the cause of failure.

• ○

  Remove the test cases from the regression suite and refer them to the test designer for manual testing for future sprints.

• ○

  Quarantine the test cases, run the regression suite without them, and perform root cause analysis on the test cases in parallel.

• ○

  Run the test cases manually now. If they still pass, keep them in the regression suite, if they fail perform root cause analysis.

Select an option, then click Submit answer.

• ○

  Complexity to automate the manual test cases

• ○

  Correctness of test data and test cases

• ○

  The look and feel of the SUT

• ○

  The controllability of the SUT
  

Select an option, then click Submit answer.

• ○

  Checking whether all the test cases contain the expected results

• ○

  Checking whether the post condition have been fulfilled for all the test cases

• ○

  Checking whether the loading of the TAS is repeatable in the SUT environment

• ○

  Checking whether all the test cases produce repeatable outcomes