How to Work with AUT Environments

This task describes how to work with AUT Environments.

1. Prerequisites

   • Which AUT environments do you need to configure?

   • What are the applications you intend to test? 

   • How many different environments will you have for each application?

   • What details do you need for each environment? For example, do you have specific URLs, user names, and passwords for each environment?

2. Create AUT environments

   1. Open the AUT Environments module. On the ALM sidebar, under Lab Resources, select AUT Environments.

   2. Create folders. Select the root AUT Environments folder or a sub-folder, and click the New AUT Environment Folder button.

   3. Add AUT Environments to folders. Select a folder and click the New AUT Environment button. Add an AUT environment for each of the applications you need to test.

      For user interface details, see New AUT Environment Dialog Box.

   4. Add AUT Parameters. Select an AUT environment and click the New AUT Parameter button in the right pane. Add a parameter for each environment parameter you need for the application you are testing. Enter the parameter name and a value in the New AUT Parameter dialog box. The value you enter in the AUT parameter dialog box will be the default value for that parameter in the selected AUT environment.

      For user interface details, see New AUT Parameter Dialog Box.

   5. Add AUT Environment Configurations. Select an AUT environment and click the New AUT Environment Configuration button. Add an AUT environment configuration for each environment you might use while testing the selected application.

      For user interface details, see New AUT Environment Configuration Dialog Box.

   6. Modify AUT Environment Configurations. Select an AUT environment configuration and override any of the default parameter values you need to adjust for this specific AUT environment configuration. You can modify the values in the right pane.

      For user interface details, see AUT Environments Module Window.

3. Link AUT environment configurations to CDA (optional)

   You can link your AUT environment configurations to Micro Focus Continuous Delivery Automation (CDA) to arrange for your tests to be provisioned and deployed dynamically. For details, see Link AUT Environments to CDA.

   Note: To use CDA, you must configure a CDA server in Lab Management. For details, see the Micro Focus ALM Lab Management Guide: How to Manage CDA Servers.

   To link an AUT environment configuration to CDA, do the following:

   1. In the AUT Environments module, select an AUT environment configuration.

   2. Click the Link to CDA button.

   3. In the Link to CDA dialog box, use the drop-downs to select a CDA topology. For user interface details, see Link to CDA Dialog Box.

   4. In the AUT Environments module, in the right pane, select a parameter in the Values tab. Select the CDA parameter to link to the selected AUT environment parameter.

4. Run tests using AUT environments

   When running a functional or performance test, you can provide an AUT environment configuration to execute your test using specific environment parameters.

   Note: AUT Environments are available only for LoadRunner Enterprise Tests, Service Test, API testing in UFT, and VAPI-XP tests.

   Use one of the following methods to execute your test using an AUT environment configuration:

   • Schedule a timeslot.

     In the Timeslots module, create a new timeslot. Select a test set to run and then select an AUT environment configuration. For user interface details, see Timeslot Reservation Dialog Box.

   • As part of a functional test set or performance test execution.

     In the Test Lab module, go to the Execution Grid tab. Select a functional test set and click Run Test Set, or select a performance test set, then a performance test, and click Run Test. In the Run <Entity> dialog box, select an AUT environment configuration. For user interface details, see Run <Entity> Dialog Box.

   • In a build verification suite.

     In the Build Verification module, select a build verification suite and click Run. In the Run Build Verification Suite dialog box, select an AUT environment configuration. For user interface details, see Run <Entity> Dialog Box.

5. Select a deployment and provisioning option (CDA only)

   Deployment: When your system is integrated with CDA, you can select deployment and provisioning actions for the application under test. ALM provides the following options in the Timeslot Reservation dialog box and the Run <Entity> dialog box for this purpose:

   • Provision and deploy. Allocates machines on which to deploy an environment for the application under test, and prepares the required image so that the application can be installed. That is, the operating system, database server and all required software are installed based on CDA parameters. Following provisioning, the application under test itself is installed.

   • Redeploy. Deploys and runs the application under test environment on machines that have already been provisioned.

   • Use deployed. Uses an existing installation to run the test.

   Note:

   • When deciding which option to select, bear in mind that the provisioning and deployment actions can be very time consuming. For routine testing, it is advisable to select Use Deployed.

   • You can arrange for an environment to be deployed and available for your run. Schedule a build verification suite or test set to run for the entire day, and select the environment you want to use.

   Available for: All options are available for Build Verification Suite timeslots. For Functional test set timeslots, Use Deployed is selected by default. You cannot change this selection.

   Provisioning: ALM also allows you to select the action to be taken after an environment has been deployed. ALM provides the following options:

   • Leave environment deployed. Leaves the AUT environment deployed indefinitely. The deployed environment can be used for future tests.

   • Deprovision at end. After the tests have completed running, the environment is undeployed and the machines are deprovisioned, freeing them up for other use.

   Available for: Build Verification and Functional test set timeslots.

   For user interface details, see Timeslot Reservation Dialog Box and the Run <Entity> Dialog Box.