Resolving Problems on and Unlocking Secondary Machines

Relevant for Power Mode only

When a secondary machine is locked, you need to solve the problem and unlock the machine so that Sprinter can continue replicating your user actions.

Sprinter provides the following operations to address problems on the secondary machine:

  • Stop/Continue Replication. When you stop replication on a secondary machine, any actions you perform on the primary machine are not kept as pending actions and will not be replicated on the secondary machine.

  • This may be useful if you need to perform actions to resolve the difference that are not part of your test on your primary machine, and that you do not want replicated. You can also use the Stop Recording button in the Tools sidebar to stop recording all your user actions on your primary machine.

  • Differences Viewer. The Differences Viewer enables you to view the details of differences that were found during a Compare All operation. From the Differences Viewer you can:

    • Submit a defect about the problem.

    • Ignore the difference.

    • Create a rule so that Sprinter ignores the difference now and in the future.

    • If you use the Differences Viewer to ignore all the differences or to create rules for all the differences, the secondary machine is unlocked and Sprinter attempts to replicate any pending actions.

  • Open Remote Desktop. You can open a remote desktop connection from the Machines sidebar or the Differences Viewer.

  • This may be useful if the problem with the secondary machine is due to a display issue that is not related to the application you are testing. You can open a remote desktop connection and correct the problem. You would then use one of the operations below to unlock the machine.

  • Show Screen. Displays a current screen capture of the secondary machine.

Sprinter provides the following operations to unlock the machine after you address the problem:

  • Skip. You can ignore the problem that Sprinter found with the secondary machine and continue replicating pending user actions.

  • Sync. You can ignore the problem that Sprinter found with the secondary machine, delete all pending actions, and synchronize the actions number with the primary machine.

  • Retry. You can try to replicate the failed user action again.

  • This may be useful if you opened a remote desktop connection to address a display issue that is not related to the application you are testing. After addressing the issue, you can try to replicate the action again.

  • Recompare. You can recompare the secondary machine with the primary machine.

  • After you resolve differences that were detected by a Compare All operation, you can Recompare the machines to confirm that there are no differences, and to unlock the secondary machine.

    If you resolved the differences between machines using the Differences Viewer, the machines are automatically recompared and unlocked when all the differences are resolved.