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 thesystem (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?

A. Maturity of the test process

B. Complexity to automate

C. Frequency of use

D. Sustainability of the automated environment

You are working on a government system called "Making Tax Digital" or MTD for short. This system is being implemented to stop manual human input error and also to reduce fraudulent behaviour from companies when submitting their tax

and VAT returns.

The key concept is that registered companies will need to use government recommended 3rd party software for their accounts and book keeping. These 3rd party applications will have a direct interface into the government's main system for

transactions and submissions.

You have been using a test execution tool successfully on the project so far. and have implemented a basic "capture/replay" approach to scripting.

The management have been encouraged with the automation so far, but want the following objectives to be met:

*

Test cases added easily

*

Reduction in the amount of scripts and script duplication

*

Reduction in maintenance costs

Which scripting technique would be MOST suitable in this scenario in order to meet the objectives?

A.

Linear scripting

B.

Structured scripting

C.

Data-driven scripting

D.

Keyword-driven scripting

In order to achieve re-use of a TAS, where SHOULD the design for reuse occur?

A. At the code level

B. At the framework level.

C. At the TAS level

D. At the TAA level

You are working as a TAE for a company who are re-designing their website. The new website provides information for customers and there are two minor features being developed:

1) Request a newsletter

2) Ability to contact the organisation with a question or comment

The website must be "mobile friendly" and available on all major web browsers.

You have been tasked to provide an automated solution for web browsers only and to concentrate on the two minor features.

What would be a KEY challenge with automation in this context?

A. A low level of intrusion is likely from use of existing UI elements, but depending on the solution this might be more complex than a higher level of intrusion.

B. Because there is a high level of intrusion there may be many false alarms.

C. Automation might not be possible on the mobile devices.

D. The benefits of automation might not be achieved for many years due to the complexities of the SUT and automation solution.

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?

A. 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.

B. Automate tests at one level only, System level. Use only the newly developed interfaces and do not create any customized interfaces/test hooks.

C. 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.

D. 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.