A common need in manual testing is running the same test scenario on different configurations. You may want to test your application on different operating systems, or in the case of a Web application, with different browsers.
When you work with mirroring, every user action you perform in your application on your primary machine is replicated on the defined secondary machines.
You decided that you want to run your test with mirroring, because you need to make sure that your online travel agency application will work on all of the popular browsers and the most common operating systems.
Normally the QA team selects a few combinations of browsers and operating systems due to limitations of time and resources. Now with mirroring, you can test many of the combinations at once.
You have arranged for a computer lab to be set up with the combinations of the supported browsers and operating systems and you have access to the machines for a few hours, which is plenty of time since you can test all the combinations simultaneously.
To work with mirroring, you select the Mirroring node in the Power Mode group and configure the secondary machines for your test. You then click the Add button to add a new machine for your application.
You provide a machine name or IP address for the secondary machine, and since you are testing a Web application, you define which browser you want to use to run the application on this machine. You decide to also provide the remote desktop connection information, in case you want to open a connection during your test (you can provide that information during the run as well). You repeat this for each machine in the testing matrix.
You need to also set up your secondary machine with the specific configuration and settings you want to test.