Team Development with Visual Studio Team Foundation Server

3. Use the Test Manager to group tests into the new Test List by dragging and dropping
the tests from the Test View to the Test List in the Test Manager.
4. Create a new Team Build type.
5. Select the check box to run automated tests.
6. Select the test project within which your tests and test list were created
7. Select the test list you want to run.
Additional Resources
• For more information about automatically running Build Verification Tests, see
“How to: Configure and Run Build Verification Tests (BVTs)” at
http://msdn2.microsoft.com/en-us/library/ms182465(VS.80).aspx
• For more information about how to run automated build tests without Visual Studio
Test Edition or a VSMDI file, see “How to run tests in a build without test metadata
files and test lists (.vsmdi files)” at
http://blogs.msdn.com/buckh/archive/2006/11/04/how-to-run-tests-without-testmetadata-files-and-test-lists-vsmdi-files.aspx
How to Run Code Analysis as Part of the Build
To turn on code analysis for a build type, you can either select the code analysis check
box in the New Team Build Type Creation Wizard when you create the new Team Build
type, or you can modify the TFSBuild.proj file after the build type has been created.
To enable code analysis in the TFSBuild.proj file
• If you want all projects to run code analysis, regardless of project settings, change the
tag to Always.
• If you want to run code analysis on each project based on project settings, change the
tag to Default.
Additional Resources
• For more information about automatic code analysis as part of the build, see “How To
– Automatically Run Code Analysis with Team Build in Visual Studio Team
Foundation Server” in this guide.
• For more information about code analysis tools, see “Guidelines for Using Code
Analysis Tools” at http://msdn2.microsoft.com/en-us/library/ms182023(VS.80).aspx
How to Get Failed Tests to Fail a Build
When a build fails because of compilation errors, a work item is created to track the
failure and the build is marked as failed. When an automated test fails, however, the build
does not fail. The test failure is converted into a warning and the build continues.
You might want to fail the build if an associated automated test fails. You might also
want to generate a work item automatically to track the failure.
To fail the build upon test failure