Testing on Multiple Machines

Note: This functionality is only available if you log in using ALM, Octane, or a UFT license.

Relevant for Power Mode only

A common testing requirement is the need to test your application's compatibility with different computer configurations, and in the case of Web applications, with different browsers.

Sprinter's Mirroring feature enables you to run your test simultaneously on multiple machines with different configurations.

A test run with mirroring has a primary machine and secondary machines:

  • Primary machine. The machine on which you manually perform all the user actions in your test.

  • Secondary machine. The machine on which Sprinter replicates your user actions.

To run a test with Mirroring, you configure each of the secondary machines with the specific configuration you want to test. After you perform each user action on your primary machine, Sprinter replicates that user action on your secondary machines.

When you configure your secondary machines, consider that Sprinter replicates your user actions the same way they were performed on your primary machine. You need to configure your secondary machines in such a way that there will not be a conflict between the actions that are performed on all the machines.

Example:

Suppose your application works with a database. When you create or modify a record in your primary machine, Sprinter will attempt to create or modify the same record when it replicates your action in the secondary machines. Therefore, you cannot use the same database schema in your primary and secondary machines.

To address this issue, you can configure each secondary machine in your run to work with its own database, or with a dedicated database schema.

You can compare your primary machine with all the secondary machines in your run, to see if there are differences in their displays. Sprinter provides a number of different options to resolve differences it detects between the displays.

To perform mirroring on secondary machines, install Sprinter on each of the machines. You do not need to provide a license for the secondary machines, since you will not be opening Sprinter on these machines—you will only be accessing the SprinterAgent.

To work with mirroring, you need to have a certain number of available Application Lifecycle Management licenses. The number of licenses you need depends on the number of secondary machines you want to use in your test. You can work with a maximum of five secondary machines in a run.

The following table describes the total number of licenses required in a run with mirroring:

Secondary Machines

Total Number of Licenses Required

1

1

2-3

2

4-5

3

This section also includes: