How to: Verify a Bug is Fixed Using Microsoft Test Manager

  • Article

If you have submitted a bug based on an existing test case, then you can verify that bug directly from the Verify Bugs view in Microsoft Test Manager. To do this, you must have an associated test result for that test case. This functionality makes it quicker to rerun the test and change the status of the bug, based on the results, and add comments to the bug.

How to Verify a Bug

You can also rerun the test directly from the Run Tests activity and then open the bug and update it based on the results from running the test.

Requirements

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

To verify that a bug is fixed

  1. Open Microsoft Test Manager.

    Note

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

  2. To run the test, choose the down-arrow on the center group switcher and then choose Testing Center.

  3. On the center group menu bar, choose Test.

  4. To view the bugs assigned to you, choose Verify Bugs.

    The Verify Bugs view is displayed. It lists all the bugs that are currently assigned to you.

  5. (Optional) To view the bugs that you created, choose Created by me.

  6. Select the bug that you want to verify, and then choose Verify.

Note

To verify a bug from this activity, there must be a test result associated with this bug. If there is no test result, the Verify button is disabled.

  1. Choose Start test to rerun this test.

    The same pairing of the test case and configuration that is stored in the associated test result is loaded into Test Runner. You can see if the test passes or fails now the bug has been fixed.

  2. (Optional) Choose the down arrow next to the attachments icon on the Test Runner toolbar.

    1. To view the current bug details, choose the bug name displayed below Bug to verify.

    2. To view the bugs created during the current session, choose Bugs created in current session.

    3. To add notes, attachments or, screenshots stored some place else, choose Add attachment.

  3. When you have completed the test, choose Save and Close to save the new test result.

    A dialog box that shows specific fields from the bug is displayed.

  4. (Optional) To change the state of the bug based on whether it is now fixed or not, choose State.

    Note

    By default, if the test passed when you ran it, State is set to Closed.

  5. (Optional) To change who the bug is assigned to, choose Assigned to.

  6. (Optional) To add a comment to the bug based on the outcome of the test, type the details in New comment.

    In the bug the comment is added to History.

  7. To save any changes you want to make to the bug, choose Save changes.

  8. (Optional) If you must add more information to the bug, choose Open bug.

    All the bug details are displayed. You can update one or more of the details and then choose Save and Close.

    Note

    Any changes to the status of the bug or who the bug is assigned to are shown in the bug list.

See Also

Concepts

Tracking and Verifying Bugs