MTM allows testers can create /organize their test plans/test cases and execute test using test runner. Also track test cases. This article will focus on how to perform manual test with MTM using SCRUM template. Below diagram shows the workflow states of the item in scrum process
1.Connect Microsoft Test Manager to your Team Project and Test Plan
Enter your TFS server link and click on ‘Add’
Once you connect to TFS ,System will prompt below window to select a test plan, If you don’t have existing test plan, create test plan by click on ‘Add’ button.(Eg-You can create a separate test plan for each sprint)
Select a test plan and click on ‘Connect now’
2. Creating and configuring test plan
2.1 Configure data and diagnostics
When running a test case, MTM helps you by automatically collecting all kinds of data that can help in reproducing and fixing bugs. This is done by using so called Data Collectors. By default, you can collect System Information like Windows version, resolution, language settings and much more
Action log – Allows you to record the actions that you perform during your test.
Event log – Collects events that your application wrote to the event logs.
IntelliTrace – Generate a file that is linked to any bug that you create.When data is collected, it gets automatically attached to the test case or any bugs created by the tester. No more struggling with testers to get all the information you need to fix a bug.
System Information– Records Information about the machine
Microsoft Test Manager allows to create test suites (within each test plan, you may have multiple test suites) and configurations that support testing your project. By using test configurations you can define how you want to run your test cases and test suites. You can group your test cases together by organizing them into a hierarchy of test suites in your test plan.As of below example you can create test suites for each sprint and releases within sprints.
3.1 Create Test suite
You can add test steps on ‘Action’ column and can add new step by clicking ‘Click here to add a step’. Also you can add expected results on ‘Expected results’ column. Make sure to add respective expected result with each steps coz when running test with each step it will display respective expected results.
Many tests require same sequence of steps to be performed for multiple test cases. As example steps for log in to the system or navigating to particular section of the system may repeat with multiple test cases within particular test suite. To avoid having to enter this sequence again and again MTM introduced ‘Shared Steps’.By creating shared steps, you can define a sequence of steps once and insert it in to many test cases.
Also if requirement change, need to change test cases accordingly. With shared steps you only have to make that change in one place and it will automatically be reflected in all the test cases that use that shared step.
3.3.1 How to create shared steps
You can create shared steps with existing steps on test cases or create shared steps separately using Organize->Shared Steps Manager
Open test case->Select sequence of steps that you want to add as shared steps ->Right click or select Shared steps icon.
Enter title for shared steps
3.3.2 Add created shared steps in to test case
Select ‘Insert shared steps’ and search for previously created shared steps
3.3.3 Edit shared steps
If requirement got change, need to change test cases accordingly. With shared steps you only have to make that change in one place and it will automatically be reflected in all the test cases that use that shared step.
Go to Organize->Shared steps Manager->Open shared steps that you need to change
3.4 Repeat a test with different data (Add Parameters to test case)
When create manual test cases we often need to run manual test case multiple time with different data.For example you might need to log in to system using different users/Select different values from particular drop down/Add different quantities of a product to a shopping cart.
You might have to create multiple copies of test cases for above scenario. Instead of creating multiple test cases, you can add parameters to the actions or expected results sections on a test case.
3.4.1 Add parameters to test case
Create a parameter using ‘@’ sign in the actions or expected results of your test case.
3.4.2 Run test case with parameters
When you come to a step that uses a parameter associated with the action, the parameter is displayed as a link within the test step. You can copy the parameter using that link and paste it in to appropriate field in the application.
Choose ‘End iteration and move next’ to execute test case with next parameter.
If one of the iteration failed during test run then outcome of the whole test is shown as failed. You can view test result for each iteration by selecting iteration on ’Details’ dropdown.
Test cases need to be in ‘Ready’ state in order to run the test case.
Go to Plan->Change test case state from ‘Design’ to ‘Ready’
Go to ‘Test’->Select test case and click on ‘Run’
Start the application that you want to run. You can mark test steps either passed or failed on the expected results. Or u can fail/pass entire test case.
If test steps failed you can enter a comment by mentioning why it failed. Also you can attached screenshots as well.
5.1 Create a Bug
Bugs entered from a test run are detailed with each step a tester took up to the moment he entered the bug, and copied automatically to the bug from the test script. These bugs are linked to the test scripts so that you can easily re-test once the bug has been resolved.
Click on the icon to create a bug
The steps and your comments are automatically added to the bug and the test case is linked to the bug.
By linking work items and other objects, you can track related work and changes made over time. Here explain how to link created issue with a test case.
Open Test case ->Click on ‘Add’ button on ‘Link’ section->Click on ‘Browse’
Enter issue ID and click on find button->Select issue id and click on ‘Ok’
You can track bugs that are assigning to you, or you can create queries to track the bugs for your team project. By using the ‘View’ drop down you can select the issues which are assign to you and verify that issues by re-running test associated with the bug and updating the bug.
You can track the progress of test suites in your current test plan immediately after you run your tests. You can view tests that have passed and failed.
You can also monitor the progress of your test plan using the test plan ->results section on MTM. This result section contains charts and numerical statistics on the test in your test plan. Results can be filtered to specify the test suites and test configurations that you want to included.
E.g.-You can view test results for specific test suite in your test plan or view for test results set to windows 7(Test configurations)
You can easily search for work items using queries. To create quires navigate to Track->Queries
Select the parameters that you want to search and click on ‘Run’
You can customize search results by adding/removing columns using column options as below.
Export to excel feature is currently not available with MTM, either you have to add plug in to MTM or u you can use Microsoft visual studio to export your test cases and created issues in to Excel.
Go to Microsoft visual studio and connect to TFS
Click on ‘New Query’ and search for work items that you want to export
Select ‘Open in Microsoft Office’ and choose ‘Open Query in Microsoft Excel’