How to: Submit an Exploratory Bug using Test Runner
When you run an exploratory test and find a bug in the application, you can submit an exploratory bug directly from Test Runner. Submitting an exploratory bug in this manner lets you specify the time range for the actions to include in the bug. The actions are recorded in an action log which can be used to create a manual test case. For more information, see How to: Use Recorded Actions to Create Test Cases.
Specifying the time range limits how much data from the diagnostic data adaptors is included in the bug as shown in the following illustration. For more information about how to configure the data adaptors see, How to: Create Test Settings for a Test Plan.
.png "Create a bug based on selected actions")
This procedure describes how to submit an exploratory bug while you run a manual test. Before you run a manual test, you must first create a manual test and add it to the test suite. You can create an exploratory test with one or multiple steps. For more information, see How to: Create a Manual Test Case and Organizing Test Cases Using Test Suites.
To submit an exploratory bug using Test Runner
In Test Manager, start to run a test. For more information, see How to: Run Manual Tests.
As you run the test case, if you have more than one test step you can mark the steps as Pass or Fail, as appropriate.
When you discover an application bug, mark the test step on which you discovered that bug as Fail.
Select the test step where the bug occurred and then click the drop-down arrow next to the Create bug button on the toolbar.
Click Create exploratory bug.
Note
You can also submit an exploratory bug at any time while you run a test, regardless if it is related or discovered during a specific test step or if a test step has failed or not.
The Time Range for Exploratory Bug dialog box is displayed.
Select the time range by moving the slider toward Now.
Note
Now indicates the time when the test was paused to create the bug. When you move the slider, the timer underneath changes to indicate the time range starting from the time that the test was paused to the time range before the pause.
The time duration displayed in this box indicates the time when actions and events occurred, excluding the pauses.
Click Use range to create bug.
The New Bug dialog box is displayed.
To see the action log for the specified range, click one of the action log file names that are displayed in the Steps to Reproduce panel.
To see the event log for the specified time range, click the event log file displayed in the Steps to Reproduce panel.
To save the bug, follow these steps:
Type an appropriate title in the Title field.
Under History, add comments specific to the bug.
(Optional) To see the test steps and detailed actions that were automatically added, click the Details tab.
(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.
Note
You can edit these test steps, expected results, and comments as needed.
(Optional) To see the system information that was automatically added about the computer that you used for the test, click the System Info tab.
(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.
(Optional) To update the priority, click the down-arrow next to Priority.
(Optional) To update the severity, click the down-arrow next to Severity.
Click Save.
Note
To create a new manual test case that you can use to retest this bug when it is fixed, see How to: Use Recorded Actions in Bugs to Create Test Cases
To close the bug, click Close.
Click Resume to resume testing.
.gif "link to video")
See Also
Tasks
How to: Submit a Bug Using Microsoft Test Manager
How to: Capture a Screenshot While Running a Test