Action Go to Start > Programs > Visual Studio 2012 > Microsoft Test Manager and launch it. Dialogue Launch the Microsoft ...

Action
Go to Start > Programs > Visual Studio 2012 > Microsoft Test Manager and launch it.

Dialogue
Launch the Microsoft Test Manager tool



Action
Specify the name of your team foundation server

Dialogue
If this is a 1st time that you are launching MTM, you will be asked to specify a TFS to connect to.



Action
Select a test plan and click on 'Select plan'

Dialogue
Select the test plan that you want to manage. 

You can now manage all the test suites, test cases, configurations and other information for your test plan.



Action
Select the Testing Center > Plan > Contents

Dialogue
To add or edit the contents of test plan, select ‘Testing Centre', ‘Plan' and then click ‘Contents'.



Action
Select a suite

Dialogue
The nodes under the test plan represent suites. 



Action
Select any test case in the right panel and say 'Open'

Dialogue
Select a test case listed in that suite and click on ‘Open' to view its contents. You will see a list of test steps with expected results.



Action
Click on close button in top right corner

Dialogue
Close the test case to go back to the plan.



Action
Go to Plan > Properties

Dialogue
Edit the properties of this test plan by going to ‘Plan' and then click ‘Properties'. The first section of the test plan properties window allows you to edit the basic properties like ‘Name', ‘Description', ‘Area path', ‘Iteration', ‘State', and so on. The ‘Run Settings' section allows you to specify how manual and automated test runs should be setup. It includes what the ‘Test environment' to use is, and even the specific build to test.



Action
Open the test setting for the manual run by clicking on the open link

Dialogue
Open the ‘Test settings' for manual testing.



Action
Select the Data and Diagnostics option on the left hand side panel

Dialogue
This option helps you select which data and diagnostic adaptors you want to use.



Action
Check the Video option

Dialogue
Selecting the ‘Video Recorder' option lets you collect video recording during your testing. Selecting the configure button lets you specify some advanced options for the selected data adapter.



Action
Click on Finish

Dialogue
Click on ‘Finish' to save your changes to the test settings and go back to plan properties.



Action
Close the plan properties window by clicking on the close button in top right corner

Dialogue
Close the plan properties activity.



Action
Select the Test Tab

Dialogue
Select the ‘Test' tab. The ‘Run Tests' window is loaded by default. This shows a similar view of the test plan hierarchy. You can select single or multiple tests to run.



Action
Select any suite and click on Run

Dialogue
Click on ‘Run', The manual test runner gets launched with the selected test cases.



Action
Check the action recording checkbox and click on start test.

Dialogue
Selecting the action recording checkbox lets you create an action recording that will allow you to replay it in the future. Click on ‘Start Test' to actually start the recording.



Action
Open the browser and browse to your application.

Dialogue
You will see a set of test steps listed in the test runner window. Follow them one by one to complete your testing. You will need to open your application first to perform testing on it.



Action
Perform the steps in the test. Mark some steps as Pass/Fail. 

Dialogue
Perform the steps of the test case and mark each step with a result. To mark the result of a test step, click the drop-down arrow next to the active icon (with a blue vertical line) to the right of the test step and then click either ‘Pass' or ‘Fail'.

The words ‘Currently Recording' appear in the title bar of each application that is being recorded. An action recording section, presented as a blue indicator, is displayed to the right of the test. The blue indicator is divided into individual sections that correspond to the steps of your test.

If you do not mark each test step as either passed or failed, then the action recording section can span several test steps. It includes all unmarked test steps since the last step that was marked as passed or failed.



Action
When you fail a step, take a screenshot and click on create bug. Fill the title; verify other details in the bug and save it

Dialogue
Since you have marked a step as failed, you would want to report it as a bug. You can take a screenshot and then click on ‘Create bug' to launch the TFS bug work item form. You can fill out the details and save it.



Action
Click End Test. Click Save and Close

Dialogue
When you have finished testing click ‘End Test'. Click ‘Save and Close' to save the test results to the server and close the test runner.



Action
Select this test case again in the Run Test window and click on Run.

Dialogue
Next, we will test this scenario again by playing the recording you just made in Test Runner.



Action
Click on Start Test and play all from the play menu

Dialogue
Instead of repeating the steps, you should replay the recording you did last time. Click the drop-down next to ‘Play' and select ‘Play all'. All the actions you performed get played back



Action
Click on End Test. Click Save and close

Dialogue
End your testing, save the test results and close Test Runner.



Action
Select the test that you just ran and click on View results from the toolbar.

Dialogue
View the results of the testing that you just did. Select the ‘View results' option and then Select the failed result to view its details. The results include attachments that were collected during the run. It also shows individual steps with their respective results. You can also open the bug that you had filed and view its details. The bug links also include rich data attachments like system info, event log, video, etc.



Action
go to Test > Do exploratory testing

Dialogue
Now let's look at a different scenario. Say you have a backlog item that your team is working on and it is now ready to be tested. You want to take a first shot at it and verify its intended behavior. For this, you go to ‘Test', 'Do exploratory testing'. This view shows the list of product backlog items that have the same area path and iteration path as that of the current test plan.



Action
Select a product backlog item and click on explore work item

Dialogue
Select a backlog item and click the 'Explore work item' button. This launches the exploratory testing window, in context of your selected backlog item.



Action
Click on start. Launch application and start doing actions

Dialogue
Click 'Start' and start testing your application, by performing actions based on the backlog item in context.



Action
After few actions, take a rectangular screenshot and add rich comments

Dialogue
After a few actions, assume that you discover a bug. Before doing anything else you want to take a screenshot so that you don't lose the repro. You take a screenshot by clicking on the camera icon in the toolbar and dragging and selecting the area that you want to capture. You can also add rich text formatted comments along with it.



Action
click on the Create Bug'  button, type a title, view other details, click on change steps, do the step selection in the change steps dialog and then save the bug

Dialogue
Now click on the ‘Create bug' button which launches the new bug work item form. And you will see that it has already prepopulated all the repro steps, comments, screenshots, attachments, video recording, etc. You just need to type a title and save the bug.

If you want to change the steps' selection in the bug, you can click the 'Change steps' link that will launch the Change Steps dialog. Here you can select the exact set of steps that you want to show in your bug form and click on ‘Select'.

After saving the bug, you are back to the exploratory testing window.



Action
Do more actions on the app

Dialogue
Continue your testing by doing more actions.



Action
Click on create test case, add title view other details and hit save and close

Dialogue
If you realize that some of the steps you are performing would make a good test case, the Exploratory Testing window provides the ability to create new test cases based on your actions.  Click the 'Create test case' button to launch a new test case work item form. Here also the test steps are already listed, you just need to add a title and then save the test case. You can also click on 'Change steps' to change the steps selection as you did for the bug form above.



Action
Click on end testing to view the session summary. Walkthrough the different sections

Dialogue
Once you are done with your testing, click on the 'End testing' button which takes you back to the test manager. Here, it shows a nice summary of your exploratory test session. It lists the bugs and test cases created, the screenshots, comments, attachments, and many other details.



Action
Open the product backlog item from the link the summary and go to its 'test cases' and 'links' tabs

Dialogue
Select the ‘View Exploratory Test Sessions' window. All the test cases and bugs you created are linked to the parent backlog item you started with.



Action
Close the backlog item and open the bug you created

Dialogue
If you open the bug you created, you will see that it has collected some rich data collectors like a text action log of the actions done, a video, system information, etc.



Action
Close the bug and go to plan > contents

Dialogue
And now when you go back to the Plan, you will see that the backlog item that you were exploring has been automatically added to Microsoft Test Manager as a requirement based suite.Also, the test cases that you created while exploring are listed under the new suite.