When you start your test with mirroring, the Health Console displays the status of each machine in your run.
When all the machines are ready, the run begins. You click the Machines tab to open the Machines sidebar and view the status of your machines.
You perform the user actions in your test and you monitor the Machines sidebar to check that all your secondary machines replicated your actions successfully.
After one action, the Machines sidebar indicates a replication failure on a secondary machine.
In this case, any subsequent user actions you perform are not replicated on the secondary machine where the failure occurred, until you address the replication problem between the machines.
You want to get a sense of what the problem is, so you right-click the secondary machine display and select Show Screen from the drop-down list to view a current screen capture of the secondary machine. You notice that on your secondary machine an ActiveX warning appeared in the browser window. Since this is not a defect in your application, you right-click the secondary machine display and open a remote desktop connection with your secondary machine and clear the warning. You close the remote desktop connection and from the right-click list you select Skip. This tells Sprinter to ignore the replication problem, unlock the secondary machine, and attempt to replicate any pending user actions (actions that were performed on the primary machine while the secondary machine still had differences).
As you continue your run, you come to a screen that has known compatibility problems between browsers. To check that the application is displaying properly, you click the Compare All button in the Machines sidebar. This compares the current display of the primary machine with the current displays of all the secondary machines and looks for differences between them.
As a result of the Compare All operation, one of the secondary machines indicates a comparison problem. You right-click the secondary machine display for that machine and select Differences Viewer from the drop-down list.
In the Differences Viewer the difference between the machines is highlighted.
You see that the difference is in the display of a user interface element between browsers, so you submit a defect for this difference. Now that you have submitted a defect, you don't want Sprinter to detect this type of difference in the future. So you create a rule in the Differences Viewer, instructing Sprinter to ignore differences of this type.
You close the Differences Viewer and return to your run. Once you resolve the difference, the secondary machine is unlocked and any pending user actions are replicated.
Now that you've walked through the basic process running a test with Mirroring, you are ready to get started using Mirroring in your Sprinter tests.