Get started with continuous testing
Team Services | TFS 2015 | Previous version
Make sure that your app still works after every check-in and build using Visual Studio Team Services. Find problems earlier by running tests automatically with each build. When your build is done, review your test results to start resolving the problems that you find.
Before you start
This overview shows how to get started by running unit tests with your build.
Check in your solution to Visual Studio Team Services. Include your test projects.
Create a build definition that builds your solution after each check-in, using continuous integration.
When you're ready to run other continuous tests, such as system tests, under more realistic conditions, create environments from physical or virtual machines that you've already set up. Then set up your build to run your app and tests in the environments that you created.
Run unit tests with your builds
Your build definition includes a test task that runs unit tests. For example, if you're building a Visual Studio solution in Team Services, your build definition includes a Visual Studio Test task. After your build starts, this task automatically runs all the unit tests in your solution - on the same build machine.
If you want to customize your test run, go to your team project to find and edit your build definition.
Edit the Visual Studio Test task:
You can add filter criteria to run specific tests, enable code coverage, run tests from other unit test frameworks, and so on. When you're done, save your build definition.
Start the build.
After the build finishes, you can review the test results to resolve any problems that happened.
Go to the build to open the build summary.
Open the test run results summary.
Compare your test results between this build and the last build.
Here you'll find changes in new, failed, and passed tests, how long these tests took to run, how long these tests have been failing, and more. Organize your test results and open bugs directly for failed tests.
To start debugging a failed test, review the resulting error and stack trace.
Next: Run other continuous tests with your builds
When you're ready to test your app more extensively under more realistic conditions, on different platforms and configurations:
Create environments from physical or virtual machines that you've already set up.
Set up your build to run your app and tests in the environments that you created.
Q & A
Q: Where can I find details about configuring test agents?
Q: How do I run tests from different unit test frameworks with my build?
A: First, set up your test frameworks in your development tool. For example, in Visual Studio:
Set up the plug-in for your test framework, if you haven't already.
Create a folder that has the custom binaries for your plug-in. (The plug-in package for your framework is a .vsix file. Change the extension to .zip so that you can unzip it.)
Add these assemblies to version control and let the build controller know where to get them.
In your build definition, provide the path to the test framework:
Q: Can I find a specific test run?
A: Yes, by finding that test run here:
Q: Can I find specific results from a test run?
A: Yes, after you find your test run, create a query to find the test results you want:
- Run Selenium tests
- Test Java applications
- Testing in Continuous Integration and Continuous Deployment Workflows
- Review continuous test results after a build
- Set up continuous testing for your builds
- Set up environments to run continuous test tasks with your build tasks
Help and support
Submit bugs through Connect, make suggestions on Uservoice, and send quick thoughts using the Send-a-Smile link in the Visual Studio, Team Services, or TFS title bar. We look forward to your feedback.