A really cool new feature in VSTS 2010 is Test Impact Analysis which let developers view what tests that are affected by the current code changes. Pieter Gheysens wrote a blog post on how to set this up in the CTP, but things have changed a bit in Beta 1 so I thought that I would show how it is done. Since it still is a bit unintuitive to enable it, it might change once again in the RTM. The reason that it is a bit unintuitive to set it up, is because you need to have the following things:
You must use Test Metadata files when running your tests. You can’t use Test Assemblies \
You must have code coverage enabled in your test settings. VSTS use the code coverage information from a test run to determine which tests that are impacted by a code change. \
You must setup a team build in TFS with test impact analysis enabled. The build will publish the test results including the code coverage information and VSTS will read information from this build.
So, lets set it up:
First you will (obviously) need a solution containing some tests. Note that I don’t explicitly write unit tests here, because it might as well for example web tests. Check in your solution. \
Enable Code Coverage for you current test settings. See my previous post on how to do this \
Create a new team build and select your solution. Then set the Analyze Test Impacts parameter to true image\
Select the Test Container TestSettings File and make sure that it is the one in which you have enabled code coverage. In the figure above, I have selected *$/Demo/LibraryWithTests/TraceAndTestImpact.testsettings *
Save the build definition and queue a new build. Make sure it finishes successfully and that the tests were executed \
Now, change some code that you know is called by one or more tests. \
Switch to the Test Impact View, that is located in the Test –> Windows submenu. First off you can select the button on the top left, called Show Impacted Tests, that will show all tests that are impacted by all your current code changes.In this case, one test was impacted (ImportedMethodTest). When you select the test, you can see in the bottom part of view what code changes that caused the impact image The next button is called Show Code Changes and shows the opposite information, e.g. what code changes that has been done, and for each code change it lists the affected test. Note that there is Run Tests link in the view. This is also available as a button. This lets you run all the tests that are affected by your code change. This is a very nice feature, that will speed up your development considerably (at least if you have many tests….) \
Check in your code change and queue a new build. When the build finishes, open the build summary. This will show you, in addition to the test and code coverage information, what tests that were impacted. image If you click the 1 code change(s) link next to the test, a dialog that lists all the methods that had impact on that test is shown image\
What about calling external test tools such as Ounce Labs (now IBM) for a source code security review? We’re evaluating TFS 2010 but also leverage Ounce as part of our Secure SDLC process
