Free ISTQB Certified Tester Advanced Level – Test Automation Engineer Exam TAE Exam Practice Test

Designing the System Under Test (SUT) for testability is important for a good test automation approach and can also benefit manual test execution.Which of the following is NOT a consideration when designing for testability?

• Observability: The SUT needs to provide interface that give insight into the system.
• Re-useability: The code written for the SUT must be re-useable for other similar system.
• Clearly defined architecture: The SUT Architecture needs to provide clear and understandable interfaces giving control and visibility on all test levels.
• Control: the SUT needs to provide interfaces that can be used to perform actions on SUT.

Consider a SUT that small run on multiple platform during the execution of automated test runs. In each test run an automated test suite needs to be executed, with the same version of the TAF, against the same version of the SUT of each platform. Each platform shall have its own dedicated test environment. Your goal is to implement a process as automated as possible ( i.e with minimal manual intervention) that allows implementing a consistent setup of the TAS across the multiple test environments.Which two of the following aspects are MOST relevant for achieving your goal in this scenario?The configuration of the TAS uses automated installation scriptsThe TAF saves the logs needed to debug errors in XML formatC) Features of the TAF not used by the automated tests have been testedD) All the automated test cases contain the expected resultsE) The TAS components are under configuration management

• A and e
• B and c
• B and d
• A and d

Consider a TAS that exclusively uses the APIs of a SUT. To make this work, significant changes have been required to the SUT by adding a set of dedicated test interfaces to the APIs. All the automated tests will use these test interfaces when interacting with the SUT. Assume that you are currently verifying the correctness of the automated test environment and test tool setup.Which of the following would you expect to be the MOST specific risk associated with this scenario?

• 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

A web application was released into production one year ago, it has regular release which follow a V-model lifecycle and testing is well-established and fully integration into the development lifecycle. You have been asked to implement a TAS for the regression test suite. The regression tests have been developed via the GUI and are expected to be run at least four times a month, for each planned release, for the whole operation solution life of the system (six years). Each screen of the GUI uses several third-party controls which are not compatible with the existing automation solutions. The environment for the automation will be stable, fully controllable and separated from other environments (development, staging, production).What could be the MOST problematic for this TAS?

• Maturity of the test process
• Complexity to automate
• Frequency of use
• Sustainability of the automated environment

You have been asked to automate a set of functional tests at system Test level via the CLI of the SUT for the first release of a software system. The automated tests will be delivered to the learn in change of maintenance testing, who will use them for part of the regression testing. They have the following requirements.1. The automated tests must be as fast and cheap to maintain as possible2. The cost of adding new automated tests must be as low as possible3. The automated tests must have a high level of independence from the tool itselfWhich of the following scripting techniques would be MOST suitable?

• Data-driven scripting
• Keyword-driven scripting
• Linear scripting
• Structure scripting

You have been asked to determine a TAS for a new release of a SUT, test should be automated wherever. The new release will consist of 5 new interfaces and an amendment to 3 existing interfaces. The new and amended interface will be deliver incrementally in 3 sprints, each lasting 2 weeks.What would be the BEST Test Automation Solution (TAS) design in this scenario?

• Automate tests at both Component and System Level. Only do this automation once every interface has been fully developed or amended and manual testing has completed successfully.
• Automate tests at one level only, System level. Use only the newly developed interfaces and do not create any customized interfaces/test hooks.
• Automate the tests at two levels, Component and System level. Create customized hooks at Component level for interface not yet developed or amended. Only use the newly developed or amended interfaces to test at System level.
• Automate a test at once level, component level, Create customized interface/test hooks for this level where the interface has not yet been developed or amended.

Your goal is to verify completeness, consistency and correct behavior of an automated test suite. The TAS has been proven to successfully install in the SUT environment. All the preliminary checks to verify the correct functioning of the automated test environment and test tool configuration, installation and setup have successfully completed.Which of the following is NOT a relevant check for achieving your goal in this scenario?

• 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

Consider a TAS that is going to be deployed for the first time. The TAS requires share resources and run it its own test environment. The infrastructure for the TAS has been created along with maintenance procedures. It is very unlikely the TAS will be required to work in other targetEnvironments. There is a high-risk that when the TAS is deployed in its own test environment, a number of existing application will no longer work because of conflicts with the existing shared resources.Which of the following activities would you expect to be MOST effective at mitigating the risk associated with the first deployment of the TAS?

• Testing the TAS for application compatibility issues in the target environment
• Testing the TAS for its ability to be implemented in other target test environments.
• Testing the TAS for regressions due to optimization that fix non-functional issues.
• Testing the TAS for ITS ability to run a shared test environment

Consider a TAS associated to dynamically changing software frequent releases. Your goal is to determine the amount of effort required to maintain the automated tests of the regression test suite for each new release of the SUT.What is the MOST important metric to collect to achieve your goal?

• The code coverage achieved with the automated tests, for each new release of the SUT
• The number of automated tests which fail because of a single software defect, for each new release of the SUT
• The time it takes to execute all the automated tests, for each new release of the SUT.
• The number of automated tests requiring maintenance, for each new release of the SUT.

Which of the following statements does NOT describe good practice for maintaining the TAS?

• 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