MultipleChoice
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?
OptionsMultipleChoice
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 scripts
*The TAF saves the logs needed to debug errors in XML format
C) Features of the TAF not used by the automated tests have been tested
D) All the automated test cases contain the expected results
E) The TAS components are under configuration management
Options