Free Certified Tester Test Automation Engineer Exam CT-TAE Exam Practice Test

A project consists of distributed teams working in a 24-hour environment, where activities happen at all hours of the day. This project adopts a CI (Continuous Integration) process when developer check-in code and consists of automated activities that include generating a build and deploying it to a test environment. Automated integration tests are run multiple times a day. The project have asked for a report containing the automation test results for every build, which must be available 24/7 to the project team. Which of the following would be the BEST way to automatically provides this report?

• Store the execution results of the integration tests for the last build to a database (without overwriting the results from the previous builds), use this database to automatically update a dashboard containing the build history and test results accessible to the project team.
• Store the execution result of the integration tests for the last build to a database (overwriting the results from the previous build), automatically create a test execution report for this build send It via e-mail to the project team
• Store the execution results of the integration tests for the last build to a database (without overwriting the results from the previous builds). Automatically create a test execution report for this build and send it via e-mail to the project team
• Store the code coverage results of the integration tests for the last build to a database (without overwriting the results from the previous builds). And automatically create a chart showing the trend in code coverage and send via email to the project team.

You have executed an automated test suite for a product that was released into production. Although all the tests passed, there was a major failure in production in an area that was covered well by your automated tests. You have run the automated tests again and one of the tests is now failing and this is directly related to the production defect that was raised. You decide to run the automated test suite again on the same version of the SUT and the test now passes. What SHOULD you do now to verify the validity of the automated tests?

• 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_Sys

You are working as a TAE for a company who have been using a web test execution tool for a number of years. The tool has been used successfully on ten web applications in the past. The company are developing a new web application which has a friendly User Interface, but the developers have used an object throughout the application which the tool is unable to recognise. As a result, you have no way of capturing the object or verifying the contents using the automation tool. What is the first thing you should do about this problem?

• See if the application can be run on a desktop and if the object can be recognised on the desktop by the tool.
• Investigate whether the object can be recognised by other test execution tools in the market
• Ask the developers to remove the object and replace it with some text fields
• Ask the developers if they can change the object to something that can be recognised by the tool

What are the four horizontal layers of the gTAA?

• Test adaptation, test execution, test design, test definition
• Test generation, test execution, test definition, test APIs
• Test generation, test definition, test execution, test adaptation
• Test definition, test execution, test reporting, test adaptation

You are testing a major enhancement to an air traffic control user interface. You have use of a sophisticated pre-production test environment, created specifically for large scale automated regression, performance and security testing. The window for regression testing is limited and must successfully conclude, with no major regressions remaining, before the non-functional testing starts. You have been using the same version of the TAS for the last few releases, each time completing the automated regression test suite in a single overnight run. However, due to the latest enhancements for the SUT, you believe there is a risk that the test suite may no longer complete overnight and therefore delay performance and security testing. Which option would be the BEST and MOST cost-efficient approach to mitigate this risk?

• Create a mirror of the pre-production test environment and split the regression test suite to run in parallel across the environments.
• Split the regression test suite into multiple parts, running in the environment across consecutive nights.
• Analyse the regression test suite and remove test coverage duplication and redundancy.
• Introduce better coding practices for the automation scripts, including coding guidelines, reviews and improved static analysis.

Consider the following layers of the gTAA structure: a. Test generation layer b. Test definition layer c. Test execution layer d. Test execution layer Consider the following capabilities associated with these layers. Acquire all the necessary resources before each test and release all after run, in order to avoid interdependences between test Allow the automated test scripts on an abstract level to interact with components, configurations and interfaces of the SUT. Design test directives that allow configuring the algorithms used to automatically produce the test cases a given model of the SUT. Allow the definition and implementation of test cases and data by means of templates and/or guidelines. Which of the following BEST matches each layer with the appropriate capability?

• a-3, b-4, c-1, d-2
• a-4, b-3, c-1, d-2
• a-4, b-3, c-2, d-1
• a-3, b-4, c-2, d-1

Which of the following statement about the implementation of automated regression testing is FALSE?

• When automating regression tests, the structure of automated tests must always be the same as the corresponding manual tests
• When automating regression tests, the corresponding manual tests should have already been executed to verify they operate correctly
• When automating regression tests, the initialization steps set the test preconditions should be automated wherever possible
• When automating regression tests, consideration should be given to how much time would be saved by automation

Consider A TAS for testing a desktop application via its GUI. All the test cases of the automated test suite contain the same identical sequences of steps at the beginning (to create the necessary objects when doing a preliminary configuration of the test environment and at the end (to remove everything created –specifically for the test itself during the preliminary configuration of the test environment). All automated test cases use the same set of assertion functions from a shared library, for verifying the values in the GUI fields ( e.g text boxes). What is the BEST recommendation for improving the TAS?

• Implementing keywords with higher level of granularity
• Improving the architecture of the application in order to improve its testability
• Adopting a set of standard verification methods for use by all automated tests
• Implementing standard setup and teardown functions at test case level

You have been asked to develop test automation for a legacy system that is going to go through a series of infrastructure migrations. The scripts will be used to verify basic functionality during these infrastructure changes Your Test Analysts have some programming skills and need a solution that is simple and fast. Maintainability of the scripts is not a consideration because no changes to the software are anticipated. Which of the following is the BEST scripting approach in this situation?

• Structured scripting
• Capture-replay scripting
• Model-Based scripting
• Linear scripting

Consider a TAS that uses a keyword-driven framework. The SUT is a web application and there is a large set of keywords available for writing the automated tests that relate to highly specific user actions linked directly to the GUI of the SUT. The automated test written with the keywords are statically analyzed by a custom tool which highlight’s repeated instances of identical sequence of keywords. The waiting mechanism implemented by the TAS for a webpage load is based on a synchronous sampling within a given timeout. The TAS allows checking a webpage load every seconds until a timeout value

• Changing the scripting approach to data-driven scripting
• Implementing keywords with a higher level of granularity
• Changing the wait mechanism to explicit hard-coded waits
• Establishing an error recovery process for TAS and SUT