Continuous Delivery
After you have a Windows build agent, in just a few steps you can define a CI build process that compiles and tests your .NET app whenever your team checks in code.
Define your process
- Specify the code you want to build and select the continuous integration (CI) trigger.
- Save the definition.
- Queue your new definition to make sure it works.
Your team now has a CI build to validate every change chcked into your codebase!
Whether your app is on-premises or in the cloud, you can automate build-deploy-test workflows and choose the technologies and frameworks, then test your changes continuously in a fast, scalable, and efficient manner.
Scenarios and capabilities:
Maintain quality and find problems as you develop
Continuous testing with Visual Studio Team Services or Team Foundation Server ensures your app still works after every check-in and build, enabling you to find problems earlier by running tests automatically with each build.
https://channel9.msdn.com/Series/Test-Tools-in-Visual-Studio/Unit-Testing-from-a-CI-Build-with-Visual-Studio-Team-Services/player
- Get started with continuous testing
- Testing in Continuous Integration and Continuous Deployment Workflows
- Learn more about build tasks
- An end-to-end example of continuous testing
Any test type and any test framework
Choose the test technologies and frameworks you prefer to use.
- Get started with Java testing.
- Get started with Selenium testing.
- Use Maven to build your Java app
- Unit testing framework plug-ins for Visual Studio
Rich analytics and reporting
When your build is done, review your test results to start resolving the problems you find. Rich and actionable build-on-build reports let you instantly see if your builds are getting healthier. But it's not just about speed - detailed and customizable test results measure the quality of your app.
