QuestionQ14

VerifiedImplementation and Deployment Strategies for Test Automation

You work for a company that develops a credit-checking software package. This product is available in three variants, each tailored to meet the lending-and-borrowing rules and attitudes of a particular group of countries. Each variant has two versions at any one time: the current live release and the next release under development. Each variant has its own test environment; these environments run on different platforms to reflect the diversity of real customer platforms.

A single TAS meets the automation needs of all three variants, with configurable features that accommodate the platform differences. The SUT’s test requirements are expanding rapidly, and the TAS frequently requires enhancement to support them. The SUT’s platforms are also subject to change, because of vendor updates or a desire to evaluate different platforms.

After every change, the TAS is reinstalled from a central repository using automated scripts that apply the configuration parameters for the target environment. After this, it has often been impossible to run tests correctly, or even at all, and the installation has had to be repeated once the cause was found. Which of the following actions are MOST likely to resolve this issue?

Explanation

Post-installation connectivity checks verify that the deployed TAS has the required connections to the SUT platform and its relevant interfaces. They expose environment-specific configuration and interoperability failures before automated tests are run, which is essential when the TAS and target platforms change frequently.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!