This documentation is archived and is not being maintained.

How to: Submit a Bug using Test Runner

When you run a manual test and discover a defect in the application under test, you can submit a bug directly from Test Runner without having to switch to Visual Studio. Submitting a bug in this manner automatically adds a link and information about your test and testing environment to the bug. 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.

Note Note

You can also have Test Runner record aspects of your manual test that you can submit with the bug. This makes the bug more usable by the person who will fix it. For more information about recording, see Recording and Playing Back Manual Tests.

If you find a bug when you are not running a specific test, you can submit a bug from Microsoft Test Manager. For example, you perform ad hoc testing and find a bug, or you notice incorrect behavior from discussion of the application under test. For more information, see How to: Submit a Bug Using Microsoft Test Manager.


  • Visual Studio Ultimate, Visual Studio Premium, Visual Studio Test Professional

Note Note

When you create a bug in Microsoft Test Manager and not in Test Runner, information is not automatically added to the bug. You must manually enter system information and the steps to re-create the bug.

Submitting bugs in Test Runner

To submit a bug from Test Runner

  1. In Test Manager, start to run a test. For more information, see How to: Run Manual Tests.

  2. As you run the test case, mark steps as Pass, as appropriate.

  3. When you discover an application defect, mark the test step on which you discovered that defect as Fail.

  4. (Optional) To type a comment for the failed test step.

    Note Note

    You can also add comments in the Comments for this test step using the Add comment to step result button in the toolbar. For more information, see How to: Add a Comment while Running a Test.

  5. (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 whole screen, choose the arrow next to Capture on the toolbar and select either Capture rectangular screenshot, Capture full screenshot or Capture window screenshot.

    The window is saved in an image file that has the .png extension. It is listed as part of the test step. To annotate this image, double-click the .png file and the file is opened. You can annotate it and save it. For more information, see How to: Capture a Screenshot while Running a Test.

    Note Note

    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. This can be useful to help a developer view what occurred when the bug was found. For more information about how to create a video recording, see How to: Include Recordings of the Screen and Voice During Tests Using Test Settings.

  6. (Optional) You can attach a file which can provide additional information to support the issue. Choose Add attachment to step result in the toolbar.

  7. Select the test step where the bug occurred and then choose Create bug icon on the toolbar.

    Note Note

    You can also submit a bug at any time while running a test regardless if it is related or discovered during a specific test step or if a test step has failed or not.

    A New Bug work item is created. The comments, screenshots, file attachments, and audio and video recordings appear under the STEPS TO REPRODUCE tab.

    Note Note

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

    Note Note

    The Test Runner is automatically paused while you create a bug.

    Tip Tip

    The New Bug work item includes a toolbar that you can use to format your text. You can use various formatting options, for example bold, underline, or color highlighting to emphasis key points in your comments.

  8. Type an appropriate title in the <Enter title here> field.

  9. (Optional) To assign the bug to a team member, choose the down-arrow next to Assigned To.

  10. (Optional) To change the state of the bug, choose the down-arrow next to State.

  11. (Optional) To change reason for the bug, choose the down-arrow next to Reason.

  12. (Optional) Type in an appropriate value or text in the textbox next to Effort.

  13. (Optional) To update the bug’s severity, choose the down-arrow next to Severity.

  14. Change the area for the bug by choosing the down-arrow next to Area.

  15. (Optional) To see the system information that was automatically added about the computer that you used for the test, choose the SYSTEM tab.

  16. (Optional) Under TEST CASES, you can view the test case you were running with Test Runner that the bug will be linked to.

  17. (Optional) Type any additional comments in the HISTORY tab.

  18. (Optional) To see the test result attachments that are added as links, for example screenshots choose the LINKS tab. This includes diagnostic trace data. For more information, see How to: Submit Bugs with Diagnostic Trace Data.

  19. To save the bug, choose Save and close.

  20. Choose Resume to continue with the test.

    You can end the test and mark it as blocked or continue with the test depending on the bug that you discovered.