Last week I gave an introduction on the new features in Visual Studio 2010. One of the things I showed was the Test Impact Analysis. Sadly my demo failed, because of a corrupt testsettings file as I found out later.
Inside of Visual Studio, this feature is used to immediately inform the developer of what tests they should run to verify the code changes they are making. You can also find the feature as part of Team Foundation Build and Microsoft Test and Lab Management, so you can collect the same information when running automated tests on your build server and even manual tests from within the lab manager! As most of my projects are large scale, only have to run a subset of tests saves us a lot of time(especially our test team).
Some interesting links:
- Enabling the Test Impact Analysis inside Visual Studio: http://blogs.msdn.com/phuene/archive/2009/12/07/test-impact-analysis-in-visual-studio-2010.aspx
- Enabling the Test Impact Analysis on the build server: http://blogs.msdn.com/phuene/archive/2009/12/09/test-impact-with-team-foundation-build-2010.aspx