Handling Replication Errors During a Run

Relevant for Power Mode only

If you run your test on multiple machines (as described in Run a Test with Mirroring), you may experience a replication error on a secondary machine.

Replication errors can occur due to differences between the displays of the primary and a secondary machine, or due to a communication error with the secondary machine.

During the time that you are handling replication errors, you may need to perform actions on your primary machine that are not part of your test. In this case you may want to stop capturing your user actions so they are not replicated on your secondary machines. For details on stopping capturing, see Tools Sidebar.

For details on how Sprinter replicates user actions, see User Action Replication.

This task includes the following steps:

  1. Determine the type of replication error

    Before you can handle a replication error, you need to understand its cause by viewing the current display of the secondary machine. You can view the secondary machine in one of the following ways:

    • Display a screen shot of the current state of a secondary machine with the Show Screen operation.

    • Open a remote desktop connection to the secondary machine.

    • You can also hover over the secondary machine display to view details of the error.

    These operations are available for each of the secondary machines in the Machines sidebar. For more details on these options, see the section on Secondary Machine Right-click Options in Machines Sidebar.

  2. Handle the error

    Once you determine the cause of the error, you can decide the best method to handle it. The following are the types of errors and options for handling them:

    • A problem with the display. This might be a message box, warning, or other object that displays in a machine, based on settings for that machine. It could also represent a defect in your application.

      • You can handle this type of error by opening a remote desktop connection to the secondary machine and performing the actions necessary to modify the display to match that of the primary machine.

      • If the problem was caused by a defect in your application, you can report it by submitting a defect. For details, see Detect and Submit a Defect.

    • A communication problem with the secondary machine.

      • A replication error may occur if the connection to the secondary machine is lost. You can use the options in the Health Console (Machines sidebar >Health Console button ) to reconnect to a secondary machine. For details, see Health Console.

  3. Unlock the secondary machine

    After you handle a replication error you need to unlock the secondary machine to continue replicating your user actions on that machine. You can unlock a machine in one of the following ways:

    • Skip. This option unlocks the machine and attempts to replicate any pending user action.

    • Sync. This option unlocks the machine and does not replicate any pending user actions. The action number is set to match the number of actions on the primary machine.

    • Retry. Retries replicating the failed user action.

    • For more details on these options, see the section on Secondary Machine Right-click Options in Machines Sidebar.