This article provides a tutorial on how to use Automated Build Studio operations to bring your TestComplete automated tests to the Amazon cloud.

Contents

Introduction

You can test your applications more thoroughly if you run your tests in different hardware and software environments. One of the possible ways to do this is to use cloud services, for example, Amazon Elastic Compute Cloud (Amazon EC2).

To run a test on in the Amazon cloud, you have to perform a number of specific actions like configuring and starting cloud computers, establishing remote connection to them, copying files to and from these computers, and so on. You can automate these actions with Automated Build Studio and use TestComplete or TestExecute to run automated tests on individual cloud computers.

Automation of all the cloud-related actions gives you the following benefits:

  • The entire cloud testing process becomes error-prone as the human factor diminishes.
  • You can easily change the number of cloud computers to be used in testing (that is, you can easily get a scalable cloud testing solution).

The automation of cloud-related operations with Automated Build Studio is easy. All the operations are configured visually, so you get things done without writing scripts or program code.

Below we’ll describe how you can use Automated Build Studio features to bring your TestComplete automated tests to the Amazon cloud.

An Example Demonstrating Cloud Test Automation

The main idea of cloud test automation with TestComplete and Automated Build Studio is that you use TestComplete to run tests on cloud computers and use Automated Build Studio to manage the operations with Amazon cloud computers.

Automated Build Studio and TestComplete in Cloud

We created a sample Automated Build Studio macro that demonstrates how you can perform all these actions. You can download it by using the link at the top of this article.

The macro demonstrates how you can use Automated Build Studio to perform the following actions:

  • Connect to Amazon EC2
  • Start the cloud computer (instance) to be used for testing
  • Upload test files and data to the instance
  • Run tests on the instance with TestComplete
  • Export test results to a file and download it from the instance to your computer
  • Stop the instance

Note: In order for you to be able to check how this macro works, you need an Amazon account. To create a new account, go to the AWS web page (http://aws.amazon.com), click Sign Up and provide you credentials and contact information. For more information on creating an Amazon account, see Amazon documentation.
The sample macro doesn’t demonstrate how to launch or terminate instances from Automated Build Studio. We assume that you will work with a launched instance that has everything prepared for testing (see below). Nevertheless, we would like to note that Build Studio has the appropriate operations for launching and terminating cloud computers and for registering and deleting machine images.

Preparing Cloud Computer for Testing

As we said above, our macro assumes that you have a launched cloud computer (instance) prepared for testing. For detailed information on launching instances and working with them, please see Amazon EC2 documentation. You can also read two articles about this on our website: Preparing Your Cloud Environment for Automated Testing and Simplifying Deployment of Test Machines for Cloud Testing.

We will quickly go through the preparation steps and highlight key points.

Step 1 - Obtaining a Key Pair and Creating a New Security Group

Before you launch a new instance, you need to create a new security group and obtain a new key pair.

A key pair includes a public and a secret key that is used to decrypt the Administrator user’s password of the launched instance.

To obtain a new key pair, do the following:

  • Sign in the AWS Management Console (https://console.aws.amazon.com/ec2/).
  • Click Key Pairs in the Navigation pane.
  • Click Create Key Pair.
  • Specify a name for the new pair and click Create.

The file storing the created key pair is downloaded to your computer.

Security groups set access permissions for instances. The security groups assigned to an instance are specified when the instance is launched. They cannot be changed later.

To create a new security group, do the following:

  • Click Security Groups in the Navigation pane.
  • Click Create Security Group.
  • Specify a name and the description for the new group and click Create.

Add new rules to the security group. In our example we use the SmartBear_Common security group that contains rules allowing connecting to the instance via RPD protocol and pinging the instance.

Step 2 - Launching a Cloud Computer (Instance)

To launch a new cloud computer (or instance, in Amazon EC 2 terms), do the following:

  • Click Instances in the AWS Management console and then click Launch Instance.
  • Navigate through the Create New Instance Wizard pages and set the parameters of the instance you want to launch:
  • Select the Amazon machine image from which you want to launch an instance.
  • Specify the availability zone in which you want to launch an instance and the instance’s type.
  • Specify the key pair and the security group that will be used for the launched instances.
  • Click Launch to launch the new instance with the specified parameters.

The launched instance is added to the list of your instances on the Instances page in the AWS Management Console.

Important: the instance Id is used to manipulate the instance. For example, our macro will use the Id to start and stop the instance (you will see this below). So, write down the instance Id to use it later.

Step 3 (Optional) - Creating a New User Account

Now we need to create a new account on the launched cloud computer. That account will be used to log on to this cloud computer for the test run.

  • Use the AWS Management console to obtain the launched instance’s Administrator user’s password and use it to connect to the instance using the Remote Desktop Connection.
  • Create a new Windows user account on your instance and add the account to the Administrator group.
  • Specify the password for the new account.

Note: You can use the default Administrator account to run tests on the cloud computer.

Step 4 - Installing IIS on the Instance

You will need to install a copy of Automated Build Studio on your cloud computer. It is needed to control the data exchange between your computer and the cloud computer (see below).

The Automated Build Studio copies will communicate via the SOAP protocol. In order for them to be able to do this, install Internet Information Services on the cloud computer. For more information on how to do this, see How to install IIS on Amazon EC2.

Step 5 - Installing TestComplete and Automated Build Studio

  • Install Automated Build Studio on your cloud computer. This is needed to control the macro execution on the cloud computer. Automated Build Studio running on your computer will connect to Automated Build Studio running on the cloud computer and will exchange data with it.

    Note: You have to install Automated Build Studio version 6.20 or later as cloud support has been introduced in version 6.20. Also, it is recommended that you install the same build of Automated Build Studio on both your computer and the cloud computer.

  • The cloud computer must also have TestComplete installed on it. The installation is performed in the same manner as it is performed in ordinary (non-cloud) environment.

    In this macro we use TestComplete version 10.

    Note that TestComplete Node-Locked licenses cannot be activated on cloud computers, so you will need a Floating User license of TestComplete. Since cloud computers are virtual machines, you will need to configure the TestComplete licensing modules installed on the cloud computer in order for them to be able to reach TestComplete’s License Manager.

    For information on activating TestComplete licenses and using TestComplete in the cloud, see TestComplete Licensing Guide.

Step 6 - Installing Other Needed Software

Install other application and utilities that you need for the test run. For instance, in our macro we use 7-Zip file packager the pack test project files and test results before transferring them, so we install that packager to the test instance.

Step 7 - Disabling the Shutdown Event Tracker

Amazon EC2 currently supports cloud computers that work under Windows Server 2003, 2008 or 2012 operating systems. When you shut down a computer in these operating systems, the system displays a window asking about the shutdown reason. This window prevents the cloud computer from closing normally and will obstruct normal functioning of automated tests in the cloud. It is recommended to disable this feature. To do this:

  • Open the command line window, type gpedit.msc in it and press Enter. This will invoke the Group Policy Object Editor window.
  • In the window, select Computer Configuration | Administrative Templates | System from the tree on the left.
  • Switch to the right part of the window, right-click the Display Shutdown Event Tracker item and choose Properties from the context menu.
  • In the ensuing Settings dialog, select Disabled and click OK to save the changes and to close the Settings dialog.

Step 8 - Stopping Your Cloud Computer

After you finished preparing your test instance, close the remote connection and stop the instance.

To stop the instance, select the desired instance in the Instances page and select Actions | Stop.

When the instance is stopped, it is stored as a snapshot and you do not have to pay for using its computing resources.

Operations for Automating Cloud Testing

Now let us examine the macro that demonstrates how to run an automated test on the test instance we have prepared.

This macro is intended for working on your computer. It includes special operations for working with the cloud computer (instance), uploading data to and from the instance and running TestComplete there. Below is a screenshot of the Automated Build Studio window with that macro opened in it:

Macro Editor

The macro performs the following operations:

  • Perform initialization actions (specify the connection settings and prepare folders).
  • Connect to the Amazon cloud.
  • Start the test cloud computer (test instance).
  • Wait until the cloud computer starts and until the Automated Build Studio service is launched.
  • Pack TestComplete test project’s files to an archive and upload this archive to the cloud computer.
  • On the cloud computer:
    • Unpack test project files.
    • Create working folders.
    • Run tests and pack result files to an archive.
  • Download the result archive from cloud computer to your computer and unpack test results.
  • Stop the test instance and disconnect from the Amazon cloud.

To perform each of these actions, the macro uses one or more special operations. Let’s go through these steps and describe them in detail.

Prerequisites

In order for the sample macro run successfully, the following requirements should be met:

  • The cloud computer should be prepared for testing as it was described in the section above.
  • The local computer must have Automated Build Studio installed. It will run the macro.
  • The test projects that you want to run on the cloud computer must reside on the local computer. They will be copied to the cloud computer automatically.
  • The local computer should have a file packager utility supported by Automated Build Studio installed (in our example we use 7-Zip packager). The file packager is used to pack multiple test projects files on the local computer to a single archive before transferring it to the cloud computers.

Now let us examine the main steps performed by the sample macro automating a cloud test.

Using Constants and Variables to Specify Operation Properties

To specify operation property values, we defined a number of macro constants and variables. They let you re-use data in operation properties and make the macro easier to change. For instance, instead of specifying a file name for each operation that uses this file, you can store the file name as a constant and refer to this constant every time when you need to specify the file name. If you need to change the file name, you only change the constant’s value rather than changing properties of several operations.

Automated Build Studio includes special dialogs for viewing and modifying variable and constant values. To view variables, choose Variables | Variables from the main menu of Automated Build Studio. To view and set constants, select Variables | Constants from the menu.

Before you run the sample macro, you should specify the constants’ values that will match your local computer and your cloud machine. To specify the constants’ values, choose Variables | Constants from the Automated Build Studio menu and then enter the values in the ensuing dialog.

We will explain the meaning of variables and constants when they are met in the macro description for the first time. We also put their description to the Appendix section below, so you can refer to it any time.

Step 0 - Initialization

Before we start working with the Amazon cloud, we need to perform some preliminary actions:

  • Define the settings for the remote connections.
  • Prepare working folders.

Initializations Operations

As these actions have to be run before the macro executes any other operation, we added them to the macro as child operations of the Initialization operation. The macro engine executes the Initialization operation and its child operations at the beginning of the macro run, before any other operation is executed.

Let’s have a close look at the initialization operations.

Defining Remote Connection Settings

The macro will use special operations for exchanging data between your computer and the cloud computer. To do this, we need to establish a connection to the cloud computer. We define the connection settings using the Setup Connections operation at the beginning of the macro:

Setup Connections

It is important to note that the operation only sets the settings of the remote connection. The connection itself will be established later by the operations that use the connection settings.

The operation lets you establish connection to any remote computer, on which Automated Build Studio is installed. To do this, you need to know the remote computer’s name or IP address and the user name and password for logging in.

To specify all these settings, double-click the operation in the macro and use the ensuing Operation Properties dialog:

Setup Connections Properties

As you can see, in our case the connection will be established via the SOAP protocol (PRC can be only used if the remote computer is in the same network, in which your computer is located. This is not the case what we typically have with cloud computers).

The Server URL property specifies the address of the Automated Build Studio Service running on the remote computer. Note that the URL includes the TestInstancePublicDNS variable (it is enclosed in % symbols). This variable specifies a public DNS of the test instance. At the initialization time the variable contains no value, but it will be initialized later after we start the cloud computer and obtain its IP address. That is, the variable will have had some value by the time the macro will execute operations that exchange data with the cloud computer, and these operations will be able to establish connection using the specified Server URL value.

The Username and the Password properties specify the credentials you want to use to log in to the cloud computer. These can be the values that you created on Step 3 when preparing the cloud computer for cloud testing. In our example, we specify these values using the TesterUserName and TesterPassword constants (you can view them in Automated Build Studio’s Options | Constants dialog).

Prepare Temporary Folders

One more initialization step is to prepare a working folder that will be used by macro operations for data exchange and a results folder that will store test results. We will use the Create Directory operation to create a new working folder. We will use the Remove Directory operation to delete the results folder.

Remove Directory

To specify folder names, we use constants. For example:

Remove Directory Properties

Of course, folder names can be hard-coded, but we use constants, as this lets us easily modify the macro when it is moved to another computer./p>

Step 1 - Connecting to Amazon EC2

To start working with Amazon EC2 services, we need to connect to the cloud. To do this, we use the Amazon EC2 Connection operation:

Step 1 operation

This operation must have a unique name specified. This name is used as a connection name by other operations that work with Amazon EC2:

Set Unique Name

To establish the connection, the operation requires an access key and a secret access keys to be specified:

Set Access Keys

We store the access keys’ values in the Connect_AccessKey and Connect_SecretAccessKey constants. You have to assign values to these constants before running the sample macro on your computer. You can get the keys on the Amazon EC2 web site:

  • Sign in the AWS Management Console (https://console.aws.amazon.com/ec2/).
  • Select Security Credentials from the toolbar.
  • Switch to the Access Keys (Access Key ID and Secret Access Key) section of the Your Security Credentials page. This section contains the keys.

For detailed information on obtaining the access keys, see Amazon EC2 documentation.

Step 2 - Starting the Cloud Computer (Test Instance)

After we established connection to the Amazon cloud, we can start the cloud computer that we prepared for testing. To do this, we use the Amazon EC2 Start/Stop/Reboot Instances operation:

Step 2 operation

To start the cloud computer (instance) we select the Start option in the Operation Properties dialog and specify the identifier of our instance (you got this identifier when preparing the instance, on Step 2):

Step 2 properties

In the Connection property we specify the name of the connection to Amazon EC2 (we created this connection on the previous step).

In the Instance IDs box we specify the identifier of the cloud computer to be run. This is the Id that you stored when launching an instance (see Step 2 - Launch a Cloud Computer). We store this value in the InstanceId constant.

Step 3 - Obtaining the Cloud Computer's IP Address

Before you begin working with the started cloud computer (instance), you need to obtain its IP address. The address is needed in order for Automated Build Studio running on your computer to be able to communicate with Automated Build Studio running on the instance.

Typically, the instances’ addresses are not persistent. The Amazon cloud engine assigns a new IP address to an instance every time the instance starts.

The Amazon cloud provides the possibility to assign persistent IP addresses to the instances (these are called elastic IPs). However, we will not use this feature and will consider most typical case - the case when the instance address changes on every start.

To obtain the instance address in this case, we will use the Amazon EC2 Instance Enumerator operation. It enumerates all or specified instances and saves the instance properties to macro variable:

Step 3 operation

In the operation properties you can specify the list of IDs of instances, which you would like to enumerate:

Step 3 properties

In our case, we have only one identifier in the list - the id of our test instance that is specified by the InstanceId constant.

On the Variables tab we specify the variable that will save the instance’s public DNS name. Using this address you can access the instance from outside of the cloud:

Step 3 properties

As you can see, we save the address to the TestInstancePublicDNS macro variable. As we said above, we use this variable to specify the Server URL property value of the Setup Connection operation.

The next If ...Then operation checks whether the public DNS of the test instance has been obtained successfully:

Step 3 check

This operation verifies the TestInstancePublicDNS variable is not empty. If variable is not empty, the public DNS was obtained successfully and the macro execution continues. Else, the macro execution stops and Automated Build Studio reports about an error.

After we stored the instance address to the TestInstancePublicDNS variable, the connection settings are fully specified and we can use special operations that will exchange data with the instance. We will describe these operations a bit later.

Step 4 - Waiting for the Instance Response

One more thing we need to do before we start working with the instance is to check whether all the operating system's services on the instance have started. To do this, we use the following two operations in the macro:

Step 4 operations

The first of these operations - Wait for Remote Computer - pings the instance and waits for its response:

The Wait for Remote Computer operation

To specify the remote computer to be checked, we use the TestInstancePublicDNS variable that contains the address of our instance that we obtained on the previous step:

The Wait for Remote Computer operation properties

On the Wait Options tab we specify the waiting time - 8 minutes. This time period should be enough for the instance to start. If the operation receives no response from the instance within this period, the macro will stop:

The Wait for Remote Computer operation properties

The Wait for Remote Computer operation "pings" the remote computer. The ping command will succeed after all the network and Internet services have been started on that computer. However, by this moment, the Automated Build Studio service may still being started. This service is used by Automated Build Studio to exchange data with remote computers. If it has not been started, the further operations will fail. So, we use additional Delay operation to give the service some more time for the launch:

The Delay operation

The Delay operation pauses the macro run for one minute. This time should be enough for the service to start. If it is not, then increase the time interval as needed:

The Delay operation properties

Step 5 - Uploading Test Projects

After we got the instance address and verified the instance has started successfully, we can upload test files to it. In real life, you may store test projects in some source control system and get them from there before running tests. Since the test project files may have some changes, you need to upload them to the test computer.

In this macro, we decided to demonstrate this situation. However, to make the demonstration simpler, we will not get the last version of test files from source control. We assume that test files are already on your computer and now you need to transfer them to your test instance in the cloud.

To transfer the files, our macro contains the following group of operations:

Step 5 operations

As you can see, they perform the following actions:

  • Pack the test files into a single archive.
  • Upload the archive to the instance.
  • Delete the archive on the local computer.

Packing files before transferring them gives you the following benefits:

  • The packed file’s smaller size allows you to reduce the transferring time and traffic costs.
  • The Upload File operation that is used to transfer files support working with one file at a time. Test projects can contain multiple files. So, instead of enumerating these files calling the Upload File operation for each of them, we pack the files and call the operation once.

To pack the files into an archive we use the Pack Files With 7-Zip operation. (Automated Build Studio supports several file packagers. We chose 7-Zip just for an example):

The Pack Files With 7-Zip operation

After the archive is ready, we transfer it to the cloud computer by using the Upload File operation:

The Upload File operation

This operation establishes a connection to the cloud computer using the settings we have specified with the Setup Connection operation and copies the specified file form the local computer to the target folder on the cloud computer:

The Upload File operation properties

In the Local file name edit box we specify the fully qualified name to the archive file that contains test project files. This is the path to the archive on your computer. In the Remote folder box we specify the folder on the remote machine (that is, on the cloud computer), to which the archive will be copied.

In the Connection box we specify the unique name of the connection we have set in the Setup Connections operation. Note that the Upload File operation can be used with any remote computer, on which Build Studio is installed, not just with cloud machines. So, for this operation our cloud computer is just a remote workstation. To connect to it we use the connection settings (CloudComputerConnection) specified by the Setup Connection operation, not by the Amazon EC2 Connect operation.

After we copied the archive to the instance, we can remove it on the current computer. To do this, we use the Delete File(s) operation:

The Delete File operation

Step 6 - Executing Tests

After we get the archive with our test project to the cloud computer, we should unpack the project files and then run the project.

To perform these actions, we use the Remote Group operation. This operation is intended for running child operations on remote computers, on which Automated Build Studio is installed. In our case the remote computer is the cloud computer:

The Remote Group operation

Below are the operation properties:

The Remote Group operation properties

As you can see, we selected the Run child operations on remote computer check box to indicate that the operations should work on the cloud computer. In the Connection field we specified the name of the connection to the cloud computer (we defined this connection with the Setup Connections operation at the beginning of the macro).

In the Working folder edit box we specify the path to the folder that reside on the cloud computer and that will be used as a working folder for the operation. This setting is required.

The Username and the Password properties specify the user account, which we will use to run the operations. This is the account that we created when preparing cloud computer for testing (see above).

Important: we also selected the Run interactive check box to specify that Automated Build Studio should create an interactive user session for the specified account. The interactive session is needed in order for the TestComplete engine to be able to simulate user actions on tested applications.

Now, let quickly go through the child operations of the Remote Group:

Step 6 child operations

The first two Create Directory operations create the working folders: the first operation creates the folder, to which we will unpack test project files, and the folder, to which TestComplete will store test results.

The next operation, Extract Files From 7-Zip File, unpacks the test project files to the working folder.

Then, we use the TestComplete 10 operation to execute the test project:

The TestComplete 8 operation

In properties of this operation we specify the path to the TestComplete project suite file --

The TestComplete 8 operation properties

On the Results tab we select the Export results to file check box and enter the file name that will store exported results:

The TestComplete 8 operation properties

Note: In our example only one TestComplete project suite is executed on the test instance. To make the sample macro portable, we use constants to specify the operation parameters. If you want to execute several project suites on the test instance, you have to modify the macro and specify different constant (or variable) values for each project suite.

Before transferring the result file from the cloud computer to your computer, we call the Pack Files With 7-Zip operation to archive this file:

Step 6 last operation

Step 7 - Downloading Test Results

Now we can get test results from the instance to your computer. On the previous step we packed the result file to an archive and now we copy this file from the instance to your computer:

Step 7 operations

Before we download the file, we use the Create Directory operation to create a folder, to which the file will be downloaded, on your computer.

Then we use the Download File operation to copy the file from the instance to your workstation. The properties of the Download File operation are similar to those of the Upload File operation:

The Download File operation properties

The Download File operation can be applied to any remote computer including cloud machines. To establish a connection to the remote computer, we use the TestInstance connection that we defined with the Setup Connection operation, not by the Amazon EC2 Connect operation.

After we downloaded the archive with test results, we create a folder, to which the test result will be extracted, and call the Extract Files From 7-Zip operation to extract the file from the archive. Then we delete the test results archive from your computer:

Step 7 other operations

Step 8 - Stopping the Instance and Finalizing the Macro Run

After we get the test results file on the local computer, all our tasks are solved and we need to finalize the macro execution:

  • Stop the cloud computer.
  • Disconnect from the cloud.
  • Clear the working folder.

Step 8 operations

Stopping the Instance

To stop the instance, we use the Amazon EC2 Start/Stop/Reboot Instance operation:

The Amazon EC2 Start/Stop/Reboot Instances operation

In the Operations Properties dialog we select the Stop option and specify the identifier of our cloud computer:

The Amazon EC2 Start/Stop/Reboot Instances operation properties

Disconnecting From the Cloud

After the instance has been stopped, we can disconnect from the Amazon cloud. To do this, we use the Amazon EC2 Disconnect operation:

The Amazon EC2 Disconnect operation

The operation properties specify the name of the connection to be closed:

The Amazon EC2 Disconnect operation properties

Enhancing the Macro

The described macro demonstrates the basic way to automate cloud testing. But Automated Build Studio offers much more features for working with cloud computers. For instance, it allows you to automate attaching "store devices" to instance, save instance snapshots, allocate elastic IPs and assign them to instance and etc. Automated Build Studio also provides more features for working with remote workstations, automating tests, managing files and so on.

You can use all these features to modify the presented sample macro and perform the automated cloud testing the way you need.

For example, you can automate the process of preparing the AMI and test instance launching. Or you can use a source control system to store your test project and obtain them to your cloud computers. You can also make a macro that generates an error report after the cloud testing is finished and sends it to an issue-tracking system.

You can even create a macro that works with several instances at once. For example, such a macro could start or launch several instances, run TestComplete on them to perform ordinary or distributed testing on those instances and get the test results to your computer. You will be able to easily scale the number of desired test instances or launch instances from the AMIs with different configurations.

Conclusion

We have described the procedure of preparing cloud computers for testing and demonstrated the sample Automated Build Studio macro that performs automated tests on a cloud computer. We hope this information will help you bring your TestComplete automated tests to the Amazon cloud.

If you don’t have Automated Build Studio or TestComplete, download them and try automating cloud operations yourself:

Appendix - List of Constants and Variables

Constants

Below is a description of constants we used in our sample macro. The constants are mentioned in alphabetical order:

Constant

Description

Connect_AccessKey and
Connect_SecretAccessKey

Specifies the access key and secret access key needed to connect to Amazon EC2.

Used by the Amazon EC2 Connect operation in the macro.

For information on how to obtain the Access Key and Secret Access Key values, see the operation description in the article.

InstanceId

Specifies the identifier of the cloud computer (instance).

Used by the Amazon EC2 Start/Stop/Reboot Instances operation in the macro to start and stop your cloud computer.

You can find the instance identifier in the AWS Management console when preparing your cloud computer for testing.

LocalTestProjectArchive

Specifies the fully qualified name of the archive file that contains the test project to be uploaded to the cloud computer.

Used by the Pack Files With 7-Zip and Upload File operation in the macro.

The constant should specify the file name relative to your local computer.

LocalTestProjectFolder

Specifies the fully qualified name of the folder that contains the test project files that will be packed to an archive and uploaded to the cloud computer.

Used by the Pack Files With 7-Zip operation in the macro.

The constant should specify the folder name relative to your local computer.

LocalTestResultsArchive

Specifies the fully qualified file name of the archive that the macro copies from the cloud computer to your workstation.

Used by the Download File operation in the macro.

The constant should specify the file name relative to your local computer.

LocalTestResultsFolder

Specifies the fully qualified name of the folder to which the macro extracts test results that it downloaded from the cloud computer to your workstation.

Used by the Extract Files From 7-Zip File operation in the macro.

The constant should specify the folder name relative to your local computer.

LocalWorkingFolder

Specifies the fully qualified name of the folder in which the macro places the packed test project files before uploading them to a cloud computer and to which it downloads the packed result files.

The folder name specified by the constant should be relative to your local computer.

RemoteTestFolder

Specifies the fully qualified name of the folder that contains test project files that were uploaded to the cloud computer by the macro and unpacked to the folder.

Used by the Extract Files From 7-Zip File and TestComplete 10 operations in the macro.

The constant should specify the folder name relative to the cloud computer.

RemoteTestProjectArchive

Specifies the fully qualified file name of the archive that contains test project files and that were uploaded to the cloud computer by the macro.

Used by the Upload File and Extract Files From 7-Zip File operations in the macro.

The constant should specify the folder name relative to the cloud computer.

RemoteTestResultsArchive

Specifies the fully qualified name of the archive file that contains the test result files.

Used by the Pack Files With 7-Zip and Download File operations in the macro.

The constant should specify the file name relative to the cloud computer.

RemoteTestResultsFolder

Specifies the fully qualified name of the folder that contains test result files.

Used by the Pack Files With 7-Zip operations in the macro.

The constant should specify the folder name relative to the cloud computer.

RemoteWorkingFolder

Specifies the folder on the cloud computer, to which the macro uploads the archive containing with test project files.

Used by the Upload File operation in the macro.

TesterPassword

Specifies the password of the user account that you use for connecting to the cloud computer.

Used by the Setup Connections and the Remote Group operations in the macro.

You can specify the password when creating a user account on the cloud computer. See Step 3 - Creating a New user Account.

TesterUserName

Specifies the user account that you use for connecting to the cloud computer.

Used by the Setup Connections and the Remote Group operations in the macro.

You can create the user account when preparing cloud computer for testing. See Step 3 - Creating a New user Account.

TestProjectFile

Specifies the name of the project suite file to be run by TestComplete on the cloud computer.

Used by the TestComplete 10 operation in the macro.

The constant should only specify the file name. The path is specified by the RemoteTestFolder constant.

TestResultsFile

Specifies the name of the file to which TestComplete will export test results on the cloud computer.

Used by the TestComplete 10 operation in the macro.

The constant should only specify the file name. The path is specified by the RemoteTestResultsFolder constant.

Variables

Variable

Description

TestInstancePublicDNS

Specifies the public DNS address of the cloud computer. This address is used by the Setup Connections operation to define the connection to the cloud computer. The variable value is specified by the Amazon EC2 Instance Enumerator operation.