QA Insights - Test management using Microsoft Test Manager [Novice to Advanced]


      Test management using Microsoft Test Manager [Novice to Advanced]


Basic Level Users:

An overview on the basic usage of Microsoft Test manager can be achieved by following the Video links shared below, listed with 4 videos to give complete insights into the basic usage.

Novice understanding of Microsoft Test Manager



Advanced Level Users:

Please follow the links below to understand how to Run tests with MTM & Visual Studio Web Portal



Diagnostic Data Adapters: Changing how Developers and Testers work together  The Test Impact Analysis using Test Impact Collector


While you are testing your application, Microsoft Test Manager can collect data that will help diagnose any fault that you might find. If you create a bug report while you’re testing, the data is automatically attached to the bug work item.



You can decide what kinds of data you want to collect from the above by configuring the corresponding Diagnostic data adapters.

The diagnostic data is collected in the test results. It will be added to a bug if you create one while performing the test.


Remote execution had introduced the concept of Diagnostic Data Adapters in Visual Studio 2010. We will jump right into working with two of our favorite Diagnostic Data Adapters: the Test Impact Collector and the Diagnostic Trace Collector. Both of these components have a part to play in how developers and testers interact in Visual Studio, making it easier for each discipline to unlock the potential of the other.

Test Impact Collector aims to bridge the gap between developers and testers to show you what needs to be tested and which tests need to be run. In the world of development and unit tests it is a fairly straightforward effort to enable code coverage and see what parts of the code have been called by your tests. The hassle of collecting coverage data, and providing consistent coverage through manual tests, is beyond the expectation for many testers. The development team often knows only by feature area what the test team has been up to, and vice versa for the test team to know what the development team has been trying to fix. The Test Impact Collector serves a vital role here by identifying for development which code changes will or will not be exercised by the test team’s existing test catalog, while it also helps testers identify which tests from that catalog they need to run in order to validate the new behavior their developers have included in a given build.


Test Impact Analysis


"Test Impact Analysis is a feature that first appeared with Visual Studio / Microsoft Test Manager 2010 and provides for the ability to recommend tests that should be re-run in response to changes that have been made at the code level. It's a very useful feature but it does need some configuration before it can be used".




7. Further Reading - All the above Summed up at one place

Note: Original knowledge source of  post is taken from Microsoft msdn pages.



Comments

Popular posts from this blog

QA's approach 2 Java - Understanding Static context

Selenium 4 absolute beginners - How to create Batch execution file

Technologies - Log4J - Create Log4j Configuration File - Where ? How ? What ?