Microsoft Test Manager is a tool that allows teams to plan, organize, track, and manage testing across their software lifecycle. It integrates with Team Foundation Server and Visual Studio to support test planning, creation of test cases and suites, manual and automated testing, defect tracking, and reporting. Some key capabilities include requirements tracing, status tracking, capturing diagnostic information during testing, and linking tests to automated test methods, builds, and virtual machine environments. It aims to support the entire testing process but requires other Microsoft tools and an initial configuration effort.

1. Microsoft Test Manager
How we can use it?
Marta Firlej
20/03/2016

2. Microsoft Test Manager
Team
Foundation
Server
Visual Studio
Test Center Lab Center
Microsoft
Test Manager

3. Testing Center
Test
Plan
Track
Organize

4. Test plan

5. Test Suites
Test suit
• Assign
requirements
• Additional test
suits
Query-based suit
• Any query can
be created to
show test cases
(TFS query
limitation)

6. Test Suites statuses
What statuses Test Suite
may have:
• In planning
• In progress
• Completed

7. Test case
The most important fields:
• Title
• Assigned To
• State (Design/Ready/Closed)
• Priority (1-4)
• Automation status (Not
Automated/Planned)
• Area
• Steps (Action/Expected Result)
• Parameters
• Summary
• Links

8. Shared steps
• Repeatable part of many test cases
• Edit Shared Step will cause change
in all test cases that was used
• Used the most at the beginning and
end of the test case

9. Test configurations
• Operating systems:
• Windows 7, 8, 2008 R2
• Web-browsers:
• IE 8, 9, 10, 11
• Not supported:
• IE 6,7
• Opera
• Safari
• Flash
• Java
• Silverlight

10. Copying and cloning test suites and test cases
Copy test case
use the same test case
Clone test case
create new test case
How ? Use CTRL+C and CTRL+V. Right click a test case and choose Create copy.
Edit
If you edit the test case in one suite changes are
made in all the other suites.
The two tests can subsequently be edited
independently of each other.
Delete test case
from User Story
If you delete a test case from a suite, you’re only deleting it from that suite.
If you delete test case from every suite, the test case is still in Team Foundation, and you can find it
with a work item query.
Additional
information
Under Links, you might want to delete
the link to the old test case.

11. Diagnostic data
• screen shots
• video recordings
• system information
• test impact
• action log
• event log
• code coverage
• ASP.NET profiler
• IntelliTrace
• network emulation

12. Manual testing
When you execute manual testing
based on test cases you can:
• Show test case steps
• Change state for every step tovpassed
or failed
• Add comment to each test step in
failed state
• Create screenshot for each test step
• Create defect from each test case
• Attach diagnostic data
• Edit test case

13. Testing from Windows Store apps
• You can test:
• Phone
• Tablet
• Other device
• Minimum Windows 8 remote device
Connect device
Use Team Web Access by using a browser
on the device or on another computer.
Test runner doesn’t interact with the
software that you’re testing.
Only installing the software on the
device is required.
Attach the device to your computer
and run the tests using MTM.
Allow to capture screenshots and
collect diagnostic data from the
device.

14. Test automation
Demo fast-forward
Test
automation
Attach
automated tests
Link a test
method to a test
case
Link a Coded UI
test to a test case
Automated build-
deploy-test
Record and play
back tests
(Fast-forward)

15. Exploratory testing
When you execute exploratory
testing you can:
• Create defect
• Create test case
• Add screenshots
Microsoft Test Manager store:
• Actions
• Screenshots
• Comments

16. Defects
Advantages:
•Automatic assignment to the requirements and
test cases (if it was created during testing)
•Display Test Steps with information when failed
•Screen shots for every test step and for defect
•Adding diagnostic data
•Attachments for defect and test case
Disadvantages:
•Lack of readability
•A lot of tabs with additional information

17. Test results
• States:
• Passed
• Failed
• Blocked
• Active
• Not applicable
• In Progress

18. Recommended Regression Tests
Preconditions:
• Using Team Foundation Build
• Using Visual Studio for source control versioning
• Setup environment as standard or SCVMM
Configure test settings to store
test data (method used)
Choose build version used for
testing
Execute manual and automation
tests
Show recommended tests

19. Lab Center
With Lab Center you can:
• Create new testing environment for testers and
developers
• Build new software version
• Implement new version of the software on test
environment
• Execute unit testing and functional testing
• Create Snapshot of the environment if it is virtual
• Automatically create defect with details and links
to the snapshot

20. Reports
In Microsoft Test Manager reports are based
on information about:
•Test cases
•Test Suites results
•Reasons why tests don’t passed
More detailed reports are available only by
Team Foundation Server.

21. Podsumowanie
Remember
• Refresh (F5)
• Filter
Advantages:
•Usability
•Support whole testing cycle
•All items from Test Plan are automatically connect to requirements
(treaceability)
•A lot of features and statuses
•Support of Exploratory Testing
•It is possible to record and display tests (fast-forward)
Disadvantages:
•Price – about 1199 USD for new license
•Dependent of other Microsoft tools like Team Foundation Server
•Hard to change according to individual testing process
•It requires initial configuration
Additional information - MSDN