Free ISTQB Certified Tester Advanced Level, Test Automation Engineering Exam CTAL-TAE Exam Practice Test

As a TAE you are evaluating a functional test automation tool that will be for several projects within your organization. The projects require that tool to work effectively and efficiently with SUT's in distributed environments. The test automated tool also needs to interface with other existing test tools (test management tool and defect tracking tool.) The existing test tools subject to planned updates and their interface to the test automated tool may not work property after these updates.Which of the following are the two LEAST important concerns related to the evaluation of the test automation in this scenario?Is the test automation tool able to launch processors and execute test cases on multiple machines in different environments?Does the test automation tool support a licensing scheme that allows accessing different sets?Does the test automation tool have a large feature set, but only part of the features will be sets?Do the release notes for the planned updates on existing specify the impacts on their interfaces to other tools?Does the test automation tool need to install specific libraries that could impact the SUT?

• A and C
• A and E
• B and E
• C and D

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 are currently designing the TAA of a TAS. You have been asked to adopt an approach for automatically generating and executing test cases from a model that defines the SUT. The SUT is a state-based and event-driven that is described by a finite-state machine and exposes its functionality via an API. The behavior of the SUT depends on hardware and communication links that can be unreliable.Which of the following aspects is MOST important when designing the TAA in this scenario?

• Looking for tools that allows direct denoting of exceptions and actions depending on the SUT events.
• Adopting a test definition strategy based on classification tree coverage for the test definition layer.
• Looking for tools that allow performing setup and teardown of the test suites and the SUT.
• Adopting a test definition strategy based on use case/exception case coverage for the definition layer.

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

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.

Which of the following statements BEST describe aspects of the SUT to consider when designing a TAA?

• All the interaction between SUT and TAS should be logged with the highest level of detail
• All the internal test interfaces of the SUT should be removed prior to the product release
• All the interface of the SUT affected by the tests should be controllable by the TAA
• All the external test interfaces of the SUT should be removed prior to the product release

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

Which of the following is NOT a technical design consideration for a TAA?

• The number of users for the SUT
• Availability of interfaces for the SUT to be testable
• Standards and Legal requirements, e.g data privacy
• Data used by the SUT, e.g configuration, users

Which of the following attributes should NOT be included in a test execution report associated with a suite of automated tests?

• Summary of the test execution results
• System/Application under test and its version
• Defect clusters identified during test execution
• Environment in which the tests have been executed

Which of the following success factors for a test automation project is TRUE?

• Automated tests must be designed to capture only the data that is strictly needed for comparing expected and actual results
• The test cases to be automated first must always be selected based on the number of times a test will need to be run
• The test cases to be automated must have a high dependency on particular data values
• Automated tests that fail due to changes in the requirements of the SUT should be promptly fixed rather than disabled from the test suite