Collect Data on a Local Machine Using Default Test Settings
If you just want to run manual tests on a local machine and do not want to collect data on another tier of your application, you can use the default test settings. The default test settings use the following diagnostic data adapters to collect data on your local machine only:
You do not have to select a set of roles in your test settings or select an environment in your test plan for this set up. This is the simplest approach when you are getting started.
.gif) Note |
|---|
If you select this approach, you do not have to create test settings for your test plans. The default settings are added when you create a test plan. |
Collect Data on a Local Machine Using Specific Data Diagnostic Adapters
If you want to run manual tests and collect data only on a local machine using different diagnostic data adapters from the default values, you must create test settings and either add them to your plan, or select to use these test settings when you run your tests using Run with options. However, you do not have to add a set of roles to your test settings. You can just use the default set of roles called Local for your set of roles. This will select a default matching environment of <Local Machine Only>.
Collect Data Remotely
If you want to run your manual tests on a local machine and collect data remotely, you must create an environment for the set of roles that represent your application under test. You must then select this set of roles in your test settings and specify what data should be collected or how to affect the test machine for each role.
The following table lists your choices for collecting data or affecting the test machine in the first two columns when you run manual tests on a local machine. The last three columns list the actions that you must perform in each case:
Choice 1: Collect data or affect the test machine | Choice 2: Diagnostic Data Adapters | Action 1: Create Test Settings | Action 2: Set of Roles To Be Defined | Action 3: Matching Environment Required |
|---|
Local machine only | | No: Use default test settings | No | <Local> is already added to your test plan |
Local machine only | Select specific adapters | Yes | Use default:<Local> | Use default: <Local Machine Only> |
Local and remote machines | Select specific adapters | Yes | Yes | Yes |
Automated Tests
If you plan to run your automated tests using Microsoft Test and Lab Manager, you must use a physical or virtual environment that contains a set of roles to run your tests from your test plan.
If you plan to run automated tests using Microsoft Visual Studio 2010, you can just run your automated tests on your local machine using test settings to collect data locally. If you want to collect data or affect the test machine for specific parts of a multi-tier application, you can select a test agent controller and test agents and add roles to use in your test settings
The following illustration shows a test agent controller and test agents that are installed on a machine for each role in an application under test and the tasks that the test agent can perform. The test agent controller manages the test agents that are registered to it.
.png)
Environments
You can create physical or virtual environments using Microsoft Test and Lab Manager. A physical environment might use physical computers or virtual machines. A virtual environment uses only virtual machines. :
To create a physical environment you must install one or many test controllers on available computers and associate each of them with Team Foundation Server. You can then install test agents on your computers. Each computer that is available to use in the environment is called a machine.
If you are using Visual Studio Team Lab Management, you can create virtual environments. These environments are created by using virtual machines. If you want to run tests using Visual Studio 2010 Ultimate, you can manually install test agents on the virtual machines, and then mark the environment as ready for testing to automatically provide the name of a test controller. You can also define the properties of the virtual machine and the roles that it can perform, just as you can for a physical machine.
When you create an environment, you select a test controller to use for that environment. You must then decide the roles that you require in your environment. A role specifies the purpose of a computer in the environment. For example, a specific role could be Web Server or Desktop Client. You select which machines to use in your environment and assign a role to that machine.