We recommend using Visual Studio 2017
This documentation is archived and is not being maintained.

How to: Submit Bugs with Diagnostic Trace Data

When you run a manual test on an application written with managed code and discover a defect, you can submit a bug that includes diagnostic trace information. This information is saved in an IntelliTrace file that has an extension of .tdlog. Other team members can use the IntelliTrace file to speed up the debugging process and isolate bugs that are difficult to reproduce. For more information, see Debugging with IntelliTrace.

You must enable IntelliTrace for a particular test. To do this, use a test setting that has IntelliTrace selected for the test plan that contains the test. For more information, see How to: Collect IntelliTrace Data to Help Debug Difficult Issues. You can also update an existing bug if you discover additional defects while you are running a test. For more information, see How to: Update an Existing Bug While using Test Runner.

Submitting bugs in Test Runner

To submit a bug from the Microsoft Test Runner with an IntelliTrace file

  1. Verify that the test you are running is contained in a test plan that has a test setting configured to include diagnostic tracing. For more information, see How to: Collect IntelliTrace Data to Help Debug Difficult Issues.

  2. In Test Manager, start the test. For more information, see How to: Run Manual Tests.

    Caution noteCaution

    The diagnostic tracing works by instrumenting a managed process. You must do this after the first test case for the run is started. If the process that you want to monitor has already started, no logs 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.

  3. As you run the test case, mark steps as passed, as appropriate.

  4. When you discover an application defect, mark the test step where you discovered that defect as failed.

  5. (Optional) To type a comment for the failed test step, type a comment in the text box next to the comments icon.

  6. (Optional) To take a screen shot for either a rectangular area you can define, the specific window associated with the application under test, or the entire screen, click the arrow next to the camera icon on the toolbar and choose either Capture rectangular screenshot, Capture window screenshot or Capture full screenshot.

    The window is saved in an image file that has the .png extension. It is listed under Attachments in the Test Step Results tab of the Properties pane.


    You can also create a video recording of the desktop session during the test. The recording will be attached as a .wmv file together with the test results.

  7. (Optional) You can attach a file which can provide additional information to support the issue. Click the paperclip icon and select the file that you want to attach.

    The document is attached and is listed under the test step.

  8. Select the test step where the bug occurred and then click the create bug icon on the toolbar.


    You can also submit a bug at any time while a test is running, regardless if the bug is related or discovered during a specific test step.

    The New Bug dialog box appears.


    You may also append the issue to an existing bug by clicking the arrow next to Create a bug on the toolbar and selecting Add to existing bug. For more information, see How to: Update an Existing Bug While using Test Runner

  9. Type an appropriate title in the Title field.

  10. To see the test result attachments including the diagnostic trace data, click the All Links tab. The listing will contain the .tdlog file.


    You can double-click the .tdlog file to view the IntelliTrace summary page.

  11. (Optional) To see the test steps and detailed actions that were automatically added, click the Details tab.

  12. (Optional) You can edit these test steps, expected results, and comments as needed.

  13. (Optional) To see the system information that was automatically added about the computer that you used for the test, click the System Info tab.

  14. (Optional) To update the priority, click Priority.

  15. To save the bug, click Save.