Merge pull request #2956 from gewarren/test-agents

Update test agent/controller config steps

Author: TrishaMc

docs/test/assign-roles-to-a-test-controller-and-test-agent.md

@@ -1,8 +1,8 @@
 ---
-title: "Assigning Roles to a Test Controller and Test Agent for Automated Testing in Visual Studio"
+title: "Assign Roles to a Test Controller and Test Agent for Automated Testing"
 ms.date: 10/20/2016
 ms.topic: conceptual
-helpviewer_keywords: 
+helpviewer_keywords:
   - "testing, walkthroughs, test controller and test agents"
   - "test agent, walkthrough"
   - "walkthroughs [Visual Studio ALM] testing"

docs/test/collect-diagnostic-information-using-test-settings.md

@@ -42,7 +42,7 @@ The following table provides an overview of the various ways that the diagnostic
 |**Code coverage:** You can create a test setting that includes code coverage information that is used to investigate how much of your code is covered by tests.|No|Yes (See Notes)|No|-   You can use code coverage only when you run an automated test from Visual Studio or *mstest.exe*, and only from the machine that runs the test. Remote collection is not supported.<br />-   Collecting code coverage data does not work if you also have the test setting configured to collect IntelliTrace information. **Note:**  This diagnostic data adapter is only applicable to Visual Studio test settings. It is not used for test settings in Microsoft Test Manager. Additionally, this adapter is for compatibility with Visual Studio 2010 test projects. **Note:**  For compatibility, the code coverage applies when automated tests are run from Microsoft Test Manager or on a remote Test agent from Visual Studio using the legacy MSTest runner.|
 |**Event log:** You can configure a test setting to include event log collecting, which is included in the test results.|Yes|Yes|Yes||
 |**IntelliTrace:** You can configure the diagnostic data adapter for *IntelliTrace* to collect specific diagnostic trace information to help isolate bugs that are difficult to reproduce. This creates an IntelliTrace file that contains this information. An IntelliTrace file has an extension of *.iTrace*. When a test fails, you can create a bug. The IntelliTrace file that is saved together with the test results is automatically linked to this bug. The data that is collected in the IntelliTrace file increases debugging productivity by reducing the time that is required to reproduce and diagnose an error in the code. From this IntelliTrace file the local session can be simulated on another computer. This reduces the risk of a bug being non-reproducible.|Yes|Yes|Yes|-   If you enable the collection of IntelliTrace data, collection of code coverage data does not work.<br />-   If you use IntelliTrace for a web client role, you must also select the ASP.NET Client Proxy for IntelliTrace and Test Impact diagnostic data adapter.<br />-   Only the following versions of IIS are supported: IIS 7.0, IIS 7.5 and IIS 8.0.|
-|**Network emulation:** You can specify that you want to place an artificial network load on your test by using a test setting. Network emulation affects the communication to and from the machine by emulating a particular network connection speed, such as dial-up. |No|Yes (See Notes)|No|You can use the network emulation diagnostic data adapter for a client or server role. You do not have to use the adapter on both these roles that communicate with each other. **Note:**  This diagnostic data adapter is only applicable to Visual Studio test settings. It is not used for test settings in Microsoft Test Manager. **Note:**  Network emulation cannot be used to increase the network connection speed. **Warning:**  If you include the network emulation diagnostic data adapter in the test settings and you intend to use it on your local machine, then you must also bind the network emulation driver to one of your machine’s network adapters. The network emulation driver is required for the network emulation diagnostic data adapter to function. The network emulation driver is installed and bound to your adapter in two ways: <ul><li>**Network emulation driver installed with Microsoft Visual Studio Test Agent:** The Microsoft Visual Studio Test Agent can be used on both remote machines and your local machine. When you install a Visual Studio Test Agent, the installation process includes a configuration step that binds the network emulation driver to your network card. For more information, see [Install and configure test agents](../test/lab-management/install-configure-test-agents.md).</li><li>**Network emulation driver installed with Microsoft Visual Studio Test Professional:** When you use network emulation for the first time, you are prompted to bind the network emulation driver to a network card.</li></ul> You can also install the network emulation driver from the command line on your local machine without installing the Visual Studio test agent by using the following command: **VSTestConfig NETWORKEMULATION /install** **Warning:**  The Network Emulation adapter is ignored by load tests. Instead, load tests use the settings that are specified in the network mix of the load test scenario.|
+|**Network emulation:** You can specify that you want to place an artificial network load on your test by using a test setting. Network emulation affects the communication to and from the machine by emulating a particular network connection speed, such as dial-up. |No|Yes (See Notes)|No|You can use the network emulation diagnostic data adapter for a client or server role. You do not have to use the adapter on both these roles that communicate with each other. **Note:**  This diagnostic data adapter is only applicable to Visual Studio test settings. It is not used for test settings in Microsoft Test Manager. **Note:**  Network emulation cannot be used to increase the network connection speed. **Warning:**  If you include the network emulation diagnostic data adapter in the test settings and you intend to use it on your local machine, then you must also bind the network emulation driver to one of your machine’s network adapters. The network emulation driver is required for the network emulation diagnostic data adapter to function. The network emulation driver is installed and bound to your adapter in two ways: <ul><li>**Network emulation driver installed with Microsoft Visual Studio Test Agent:** The Visual Studio Test Agent can be used on both remote machines and your local machine. When you install a Visual Studio Test Agent, the installation process includes a configuration step that binds the network emulation driver to your network card. For more information, see [Install and configure test agents](../test/lab-management/install-configure-test-agents.md).</li><li>**Network emulation driver installed with Microsoft Visual Studio Test Professional:** When you use network emulation for the first time, you are prompted to bind the network emulation driver to a network card.</li></ul> You can also install the network emulation driver from the command line on your local machine without installing the Visual Studio test agent by using the following command: **VSTestConfig NETWORKEMULATION /install** **Warning:**  The Network Emulation adapter is ignored by load tests. Instead, load tests use the settings that are specified in the network mix of the load test scenario.|
 |**System information:** A test setting can be set up to include the system information about the machine on which the test is run.|Yes|Yes|Yes||
 |**Test impact:** You can collect information about which methods of your applications code were used when a test case was run. This can be used together with changes to the application code that was made by developers to determine which tests were affected by those development changes.|Yes|Yes|Yes|-   If you are collecting test impact data for a web client role, you must also select the ASP.NET Client Proxy for IntelliTrace and Test Impact diagnostic data adapter.<br />-   Only the following versions of IIS are supported: IIS 7.0, IIS 7.5 and IIS 8.0.|
 |**Video Recorder:** You can create a video recording of your desktop session when you run a test. The video can help other team members isolate application issues that are difficult to reproduce.|Yes|Yes (See Notes)|Yes|-   If you enable the test agent software to run as a process instead of a service, you can create a video recording when you run automated tests.|

docs/test/how-to-select-a-load-test-results-repository.md

@@ -24,8 +24,6 @@ You are not limited to a local results store. Frequently, load tests are run on
 
 Test results from your agents or your local computer can be saved to any SQL server on which you have created a load test results store. In either case, you must identify where you want to store your load test results by using the **Administer Test Controllers** window.
 
-For more information about agents, see [Test controllers and test agents](configure-test-agents-and-controllers-for-load-tests.md).
-
 ## Identify a results store for load test data
 
 1.  In **Solution Explorer**, open your load test file.

docs/test/how-to-set-up-your-test-agent-to-run-tests-that-interact-with-the-desktop.md

@@ -1,6 +1,6 @@
 ---
-title: "Configure a Visual Studio Test Agent to Run Tests that Interact with the Desktop"
-ms.date: 10/20/2016
+title: Configure a test agent
+ms.date: 09/18/2018
 ms.topic: conceptual
 helpviewer_keywords:
   - "agents, configuring for interaction with desktop"
@@ -13,7 +13,7 @@ ms.technology: vs-ide-test
 ---
 # How to: Set up your test agent to run tests that interact with the desktop
 
-If you want to run automated tests that interact with the desktop, you must set up your agent to run as a process instead of a service. For example, if you want to run a coded UI test remotely using a test controller and test agent, or you want to run a test and capture a video recording when you run it, you must set up your agent to run as a process. When you assign agents to roles in your test settings using Visual Studio, or you assign agents to roles in your environment by using Microsoft Test Manager, you must change the set up for any agents assigned to roles that have to interact with the desktop.
+If you want to run automated tests that interact with the desktop, you must set up your agent to run as a process instead of a service. For example, if you want to run a coded UI test remotely using a test controller and test agent, or you want to run a test and capture a video recording when you run it, you must set up your agent to run as a process. When you assign agents to roles in your test settings using Visual Studio, or you assign agents to roles in your environment by using Microsoft Test Manager, you must change the setup for any agents assigned to roles that have to interact with the desktop.
 
 > [!WARNING]
 > If you use Microsoft Test Manager to set up a lab environment, it installs the test agent. You can specify in the **Environment Creation Wizard** that you want to configure one of the roles to run coded UI tests.
@@ -26,59 +26,48 @@ If you are running coded UI tests that start a browser, the service account for
 > [!IMPORTANT]
 > If you are running a coded UI test that starts a browser as part of a build definition, the service account for the build service is used to start that browser. This service account must be the same as the user account that is the active user on this computer. If it is not the same user account, the browser will not start.
 
- Use the following procedure to set up any agents that are assigned to a role that performs a task that needs to interact with the desktop.
+Use the following procedure to set up any agents that are assigned to a role that performs a task that needs to interact with the desktop.
 
 ## To set up an agent to run as a process
 
-1.  To configure the test agent you have installed to run as a process, go to **Start**, **All Programs**, **Microsoft Visual Studio**, **Microsoft Visual Studio Test Agent Configuration Tool**.
+1. To configure the test agent you have installed to run as a process, go to **Start** > **Test Agent Configuration Tool**.
 
-     The **Configure Test Agent** dialog box is displayed.
+   The **Configure Test Agent** dialog box is displayed.
 
-2.  To view the page to select to run as a process, choose **Run Options**.
+   ![Configure Test Agent for Visual Studio](media/configure-test-agent.png)
 
-     The page that enables you to choose to run the agent as a process or a service is displayed.
+2. Select **Interactive Process**. The test agent will be started as a process instead of a service. Choose **Next**.
 
-3.  Select **Interactive Process**. The test agent will be started as a process instead of a service. Choose **Next**.
+3. Enter the user name and password for the user that will run the test agent process.
 
-     You can now enter the details for the user to use when you start the test agent as a process, and other options.
+   > [!NOTE]
+   > - The user who you add to start the process must also be added as a member of the TeamTestAgentService group on the computer for the test controller for this agent. If this user is the current user, when you add this user to the test controller computer you must log off or reboot.
+   - Null passwords are not supported for user accounts.
+   - If you want to use the IntelliTrace or the network emulation data and diagnostic adapter, the user account must be a member of the Administrators group. If the machine that is running the test agent is running an OS that has Least-Privileged User Account, you have to run it as an administrator also (elevated). If the agent user name is not in the agent service it will try to add it, which requires permissions on the test controller.
+   - The user trying to use the test controller must be in the test controller's Users account or they won't be able to run the tests against the controller.
 
-    > [!NOTE]
-    > The user who you add to start the process must also be added as a member of the TeamTestAgentService group on the computer for the test controller for this agent. If this user is the current user, when you add this user to the test controller computer, you must log off or reboot this computer.
+4. To make sure that a computer that has a test agent can run tests after rebooting, you can set up the computer to sign in automatically as the test agent user. Select **Log on automatically**. This will store the user name and password in an encrypted form in the registry.
 
-4.  Type the name in **User name**.
+   > [!NOTE]
+   > When you are connected to the lab environment using a remote desktop or guest-based connection, you might experience frequent, unexpected disconnects. One possible cause of the loss of the connection is that the machine is configured to automatically log onto the network.
 
-5.  Type the password in **Password**.
+7. To make sure that the screen saver is disabled because this might interfere with any automated tests that must interact with the desktop, select **Ensure screen saver is disabled**.
 
-     **Important user account information:**
+   > [!WARNING]
+   > There are security risks if you log on automatically or disable the screen saver. By enabling automatic log on, you enable other users to start this computer and to be able to use the account that automatically logs on. If you disable the screen saver, the computer might not prompt for a user to log on to unlock the computer. This enables anyone to access the computer if they have physical access to the computer. If you enable these features on a computer, you should make sure that these computers are physically secure. For example, these computers are located in a physically secure lab. If you clear **Ensure screen saver is disabled**, this does not enable your screen saver.
 
-    -   Null passwords are not supported for user accounts.
+   To change the agent back to run as a service, you can use this tool and select **Service**.
 
-    -   If you want to use the IntelliTrace or the network emulation data and diagnostic adapter, the user account must be a member of the Administrators group. If the machine that is running the test agent is running an OS that has Least-Privileged User Account, you have to run it as an administrator also (elevated). If the agent user name is not in the agent service it will try to add it, which requires permissions on the test controller.
+8. To apply your changes, choose **Apply Settings**.
 
-    -   The user trying to use the test controller must be in the test controller's Users account or the they will not be able to run the tests against the controller.
-
-6.  To make sure that a computer that has a test agent can run tests after rebooting, you can set up the computer to log on automatically as the test agent user. Select **Log on automatically**. This will store the user name and password in an encrypted form in the registry.
-
-    > [!NOTE]
-    > When you are connected to the lab environment using a remote desktop or guest-based connection, you might experience frequent, unexpected disconnects. One possible cause of the loss of the connection is that the machine is configured to automatically log onto the network.
-
-7.  To make sure that the screen saver is disabled because this might interfere with any automated tests that must interact with the desktop, select **Ensure screen saver is disabled**.
-
-    > [!WARNING]
-    > There are security risks if you log on automatically or disable the screen saver. By enabling automatic log on, you enable other users to start this computer and to be able to use the account that automatically logs on. If you disable the screen saver, the computer might not prompt for a user to log on to unlock the computer. This enables anyone to access the computer if they have physical access to the computer. If you enable these features on a computer, you should make sure that these computers are physically secure. For example, these computers are located in a physically secure lab. If you clear **Ensure screen saver is disabled**, this does not enable your screen saver.
-
-     To change the agent back to run as a service, you can use this tool and select **Service**.
-
-8.  To apply your changes, choose **Apply Settings**.
-
-     A **Configuration summary** dialog box is displayed that shows the status of each of the steps to configure your test agent.
+   A **Configuration summary** dialog box is displayed that shows the status of each of the steps to configure your test agent.
 
 9. To close the **Configuration summary** dialog box, choose **Close**. Then choose **Close** again to close the **Test Agent Configuration Tool**.
 
-    > [!NOTE]
-    > There is a notification area icon that runs on the computer for a test agent that is running as a process. It shows the status of the test agent. You can start, stop or restart the agent if it is running as a process using this tool. To start the test agent as a process if it is not running, choose **Start**, **All Programs**, **Microsoft Visual Studio**, **Microsoft Visual Studio Test Agent**.
+   > [!NOTE]
+   > There is a notification area icon that runs on the computer for a test agent that is running as a process. It shows the status of the test agent. You can start, stop or restart the agent if it is running as a process using this tool. To start the test agent as a process if it is not running, choose **Start** > **Visual Studio** > **Microsoft Visual Studio Test Agent**.
 
-     If the test controller for this test agent is registered with Team Foundation Server, the status of a test agent that is running as an interactive process is displayed in the **Controllers** view in the **Lab Center** for Microsoft Test Manager. It is listed with a preceding asterisk symbol to denote that it is running as an interactive process. To restart this test agent you must use the tool that runs on the computer for the test agent and not the **Controllers** view.
+   If the test controller for this test agent is registered with Team Foundation Server, the status of a test agent that is running as an interactive process is displayed in the **Controllers** view in the **Lab Center** for Microsoft Test Manager. It is listed with a preceding asterisk symbol to denote that it is running as an interactive process. To restart this test agent, you must use the tool that runs on the computer for the test agent and not the **Controllers** view.
 
 ## See also