One of the key areas of focus for Visual Studio Team System 2010 is to enhance the experience for testers. There’s already lots of overview information on many of the new features out there so I’m going to dive right in to one of my favorite new features.
In short, the Test Impact Analysis feature gives you a list of recommended tests based on the changes that were made in a build. As you run your tests through Microsoft Test Manager (MTM) you will have the option to run the Test Impact Data Collector which is one of the many built-in Data Collectors available while running tests. This particular data collector will associate the code paths you execute in your application with the test you are running.
When Team Build generates a new build it will analyze what code has been changed since the last build was done and then provide you with a list of the impacted tests. These are the tests that touch the same pieces of code that were changed since the last build.
For a more thorough explanation of the Test Impact Data Collector read this blog post by Amit Chatterjee.
The first thing you need is an Application Under Test, for this walk-through I’ll use a simple calculator application. I’ll have a C# Class Library with some simple Add, Subtract, Multiply, and Divide functions and a C# Windows Forms project that will provide some input fields for the numbers and some buttons that call the library function. I’ll skip the creation of this sample application, you an use the attached sample application, mock up something similar or follow along with your own test application.
That’s it for this post, I look forward to any questions or comments you may have. If you have any questions on some of the steps above try looking them up on the MSDN site. Topics such as creating builds, queuing builds, etc. should be well covered there.