[This documentation is for preview only, and is subject to change in later releases. Blank topics are included as placeholders.]
Using Microsoft Test and Lab Manager or Microsoft Visual Studio 2010 you can configure the diagnostic data adapter for IntelliTrace to collect specific diagnostic trace information. Using this adapter, the test can collect significant diagnostic events for the application that a developer can use later to trace through the code to find the cause of a bug. For more information, see Including Diagnostic Trace Data with Bugs that are Difficult to Reproduce.
Note |
|---|
IntelliTrace only works on an application written with managed code. If you are testing a Web application that uses a browser as a client, you should not enable IntelliTrace for the client in your test settings, because there is no managed code to trace. In this case, you may want to set up an environment and collect IntelliTrace data remotely on your web server. For more information about environments, see Setting Up Test Machines to Run Tests or Collect Data. |
The IntelliTrace data is stored in a file that has an extension of .tdlog. When you run your test and a test step fails, you can create a bug. The IntelliTrace file containing the diagnostic information is automatically attached 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 your code. Additionally, because you can share the IntelliTrace file together with another individual who can replicate your local session on their computer, it reduces the probability of a bug being non-reproducible.
Caution |
|---|
If you enable IntelliTrace in your test settings, collecting code coverage data will not work. |
The diagnostic data adapter for IntelliTrace does not create an IntelliTrace file when a test pass is successful. It only creates a file on a failed test case or if you submit a bug.
Caution |
|---|
The diagnostic data adapter for IntelliTrace works by instrumenting a managed process, which must be done after the first test case for the run is started. If the process that you want to monitor has already started, no IntelliTrace files will be collected because the process is already running. To circumvent this, either make sure that the process is stopped before you start your first test, or restart the process after the test has begun. |
The following procedure describes how to configure the Intellisense data that you want to collect. These steps apply to both the configuration editor in Microsoft Test and Lab Manager and Microsoft Visual Studio 2010.
Note |
|---|
The diagnostic data adapter for IntelliTrace can be used with either manual or automated tests. |
Configure the Data to Collect with the IntelliTrace Diagnostic Data Adapter
Before you perform the steps in this procedure, you must open your test settings from either Microsoft Test and Lab Manager or Microsoft Visual Studio 2010, and then select the Data and Diagnostics page.
To configure the data to collect with the IntelliTrace Diagnostic Data Adapter
Select the role to use to collect IntelliTrace data.
Select IntelliTrace.
If you are adding IntelliTrace for a Web client role, you must also select ASP.NET Client Proxy for IntelliTrace and Test Impact.
This proxy enables you to collect information about the http calls from a client to a Web server for the IntelliTrace and Test Impact diagnostic data adapters.
Click Configure for IntelliTrace to modify default IntelliTrace settings.
The dialog box to configure the data that will be collected is displayed.
Caution |
|---|
If you enable collecting IntelliTrace data, collecting code coverage data will not work. |
Click the General tab. Select either Diagnostic events only to record significant diagnostic events with minimal impact on performance when you test.
-or-
Select Diagnostic events and call information to record diagnostic events and method level tracing showing call information. This level of tracing might have performance impact when you run your tests.
If you want to collect data from your ASP.NET application that is running on Internet Information Services, select Collect data from ASP.NET applications that are running on Internet Information Services.
Click the Modules tab; select either Collect data from all modules except for the following and use Add to add to the list of modules and Remove to remove a module. This option lets you include all the modules running on the system except the modules that you specify.
-or-
Select Collect data from only the following modules and use Add to add to the list of modules and Remove to remove a module. This option lets you specify exactly which modules you want.
Note |
|---|
If you can select the specific processes that you want to monitor, it is the recommended practice for performance purposes. |
Click the Processes tab. Select either Collect data from all processes except for the following and use Add to add to the list of processes and Remove to remove a process. This option lets you include all the processes running on the system except the processes that you specify.
-or-
Select Collect data from specified processes only and use Add to add to the list of processes and Remove to remove a process. This option lets you specify exactly which processes you want.
(Optional) Click the Diagnostic Events tab. Select or clear each diagnostic event category that you want included or excluded when you collect diagnostic events.
(Optional) Expand each diagnostic event category and select or clear each specific event that you want included or excluded in the diagnostic events.
(Optional) Click the Advanced tab. Next, click the arrow next to Maximum amount of disk space for recording and select the maximum size that you want to allow for the IntelliTrace file to use.
If you are using Microsoft Test and Lab Manager, click Save. If you are using Visual Studio, click OK. The IntelliTrace settings are now configured and saved for your test settings.
Note |
|---|
To reset the configuration for this diagnostic data adapter, click Reset to default configuration for Visual Studio and Reset to default for Microsoft Test and Lab Manager. |
Tasks
Concepts
Other Resources