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?

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?

As a TAE you are evaluating a functional test automation tool that will be for several projects within yourorganization. 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 testautomation 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?