Share via

How to: Submit a Bug Using Microsoft Test Manager

  • Article

You can submit a bug from Microsoft Test Manager without having to switch to Visual Studio. For example, you perform ad hoc testing and find a bug, or you notice incorrect behavior from discussion of the application under test. You can submit a bug from Microsoft Test Manager as shown in the following illustration.

Submitting a bug in Microsoft Test Manager

In addition, you can submit a bug from your test results. In this case, any information that is collected or associated with the test results is automatically added to the bug.

Note

When you submit a bug, the system information for the computer is collected at this point and attached to the bug. Otherwise, the system information is collected when you end the test or the iteration, and then it is attached to the test results.

Later, if you create a bug from these test results after the test was run, the system information added to the bug is the system information that was collected when the test or iteration ended.

Use the following procedures to submit a bug from Microsoft Test Manager:

  • Submit a bug from the Verify Bugs view

  • Submit a bug from the test results for a test

Note

When you create a bug from Test Runner, the action, details, and procedural step information are automatically attached to the bug. For more information, see How to: Submit a Bug using Test Runner.

To Submit a Bug from the Verify Bugs View

You must manually enter system information and the steps to re-create the bug with this procedure.

To submit a bug from the verify Bugs view

  1. Open Microsoft Test Manager.

    Note

    To display the Microsoft Test Manager window, click Start, and then click All Programs. Point to Microsoft Visual Studio 2010 and then click Microsoft Test Manager 2010.

  2. Click the down-arrow on the center group switcher and then select Testing Center.

  3. In the center group menu bar, click Test.

  4. Click Verify Bugs.

  5. To submit a bug, click New in the toolbar.

  6. Type an appropriate title in Title.

  7. Click Area to select the appropriate area in the team project for this bug.

  8. Click Iteration to select the appropriate iteration for this bug.

  9. (Optional) To select the user to assign to this bug, click Assigned to.

  10. (Optional) To change the state of this bug from the default state of active, click State.

  11. (Optional) To enter the reason for this bug, click Reason.

  12. To assign a priority to the bug, click Priority.

  13. To assign a severity to the bug, click Severity.

  14. To enter the details to re-create the bug, click Details.

  15. (Optional) To enter the system information, click System Info.

  16. (Optional) To link this bug to specific test cases, click Test Cases. Click Add and then click Browse to search for the test cases to link to this bug.

  17. (Optional) To add attachments to this bug, click Attachments. Any file can be added. For example, you could add a video recording file, a screen shot file or a log file.

  18. To save the bug, click Save and Close on the toolbar.

To Submit a Bug from Test Results for a Test

To submit a bug from test results for a test

  1. Open Microsoft Test Manager.

    Note

    To display the Microsoft Test Manager window, click Start, and then click All Programs. Point to Microsoft Visual Studio 2010 and then click Microsoft Test Manager 2010.

  2. Click the down-arrow on the center group switcher and then select Testing Center.

  3. In the center group menu bar, click Test.

  4. Click Run Tests.

  5. To select the test that has associated test results to use when you create the bug, right-click the test and then click View results.

  6. To create a bug, select the test result to use and then click Create bug.

    The New bug activity is displayed and the information and the attached files associated with the test result are automatically added to the bug.

  7. Type an appropriate title in Title.

  8. Click Area to select the appropriate area in the team project for this bug.

  9. Click Iteration to select the appropriate iteration for this bug.

  10. (Optional) To select the user to assign to this bug, click Assigned to.

  11. (Optional) To change the state of this bug from the default state of active, click State.

  12. (Optional) To enter the reason for this bug, click Reason.

  13. To assign a priority to the bug, click Priority.

  14. To assign a severity to the bug, click Severity.

  15. To enter the details to re-create the bug, click Details.

  16. (Optional) To enter the system information, click System Info.

  17. (Optional) To link this bug to specific test cases, click Test Cases. Click Add and then click Browse to search for the test cases to link to this bug.

  18. (Optional) To add attachments to this bug, click Attachments. Any file can be added. For example, you could add a video recording file, a screen shot file, or a log file.

  19. To save the bug, click Save and Close on the toolbar.

See Also

Tasks

How to: Submit a Bug using Test Runner

Concepts

Submitting Bugs