Your project is transitioning from manual to automated testing. You have decided to implement a pilot project so that lessons learned can inform future time estimates and schedules.
Which two of the following represent the types of test cases that are MOST suited to a test automation pilot project?
a) High added value test cases that require little effort to automate.
b) Test that are run infrequently as these will be simpler to automate
c) Reliability test cases that can show added value soon
d) Technically challenging test cases to provide the best validation of manual test conversion e) Tests that are least Important to the business as these are safer to trial
Your company is new to test automation and as TAE. you have designed a TAS which successfully supports the SUT for the current project.
There are other systems currently in operation which have been tested manually and more systems are planned over the coming years. Based on this success, your company requires test automation be rolled out to other current and future SUTs with consistency being a key objective.
Which of the following is the BEST way to achieve that?
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 TAS uses a commercial test automation tool and the default logs generated by the inconsistent formats such as different types of messages (pass/fail steps, screenshots, warnings, etc.) To solve this issue some custom logging functions have been created from the test scripts, making it possible to log the different types of messages with the same format. However, this may cause a problem due to excessive size of the logs which can make it difficult to find the required information. Assume that all the default logs will be disabled when running the automated tests and that some tests will not generate excessively sized logs.
Which of the following represents the BEST suggestion for implementing the custom logging functions?
You are working on a TAS for standalone application. The automated tests are developed based on a automation framework that allows interaction with GUI elements using on object orientated API. The GUI elements include menus, buttons, radio buttons, text toolbars and their properties.
Whilst automating a test, you have discovered that the GUI elements of some third party components are not identifiable by the automated tool you are using.
Which of the following is the FIRST step that you take to investigate this issue?
