Click to Rate and Give Feedback
MSDN
MSDN Library
Running Tests
 How to: Submit a Bug using Test Run...
Collapse All/Expand All Collapse All
How to: Submit a Bug using Test Runner

[This documentation is for preview only, and is subject to change in later releases. Blank topics are included as placeholders.]

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

NoteNote

You can also have the 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 and Lab 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 and Lab Manager.

NoteNote

When you create a bug in Microsoft Test and Lab Manager, 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 the Microsoft Test Runner

  1. In Test and Lab 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.

    NoteNote

    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: Attach 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 entire screen, click the arrow next to Capture on the toolbar and choose 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 under Attachments in the Test Step Results tab of the Properties pane.

    NoteNote

    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 for isolating bugs among team members.

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

  7. Select the test step where the bug occurred and then click Create a bug button on the toolbar.

    NoteNote

    You can also submit a bug at anytime 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.

    The New Bug dialog box appears.

    NoteNote

    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

  8. Type an appropriate title in the Title field.

  9. Under History, add comments specific to the bug.

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

  11. (Optional) To see the input data, expected and actual results, comments, and attachments that were added to a specific test step, locate the test step where you added the bug.

    NoteNote

    You can edit these test steps, expected results, and comments as needed.

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

  13. (Optional) To see the attachments that were automatically added, click the Attachments tab.

  14. (Optional) To see the test result attachments, click the All Links tab. This includes diagnostic trace data. For more information, see How to: Submit Bugs with Diagnostic Trace Data.

  15. (Optional) To update the priority, click the down-arrow next to Priority.

  16. (Optional) To update the severity, click the down-arrow next to Severity.

  17. To save the bug, click Save.

  18. Click Close.

© 2009 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement
Page view tracker