From builds to done with Vs2010
Working in cycles |
−Enforce “Done” for each cycle
−Check-in Policy
−Gated Check-in
−Continuous Integrations
−Automated build (Automated builds are the pillar of “Done” ;VS & TFS makes automated builds simple;Fully extensible )
−Validated Check-ins
−Automated unit & acceptance tests
−Automated deployment & acceptance test verification
−Reporting of “Done” metrics
Continuous integrations:
−Continuous Integration (CI) let’s you continually check for regressions
−VS & TFS has built in support for CI
−No more build breaks with Gated Check-in
−Guarantees no code ever gets in that doesn’t meet at least some “Done” criteria
−Being able to run the application is key to being “Done”
−The 2010 release will include new virtualized lab management tools
−Integrate builds and lab deployment
Automated testing
−Automated tests lets you stay “Done”
−Visual Studio 2010 lowers the barrier and cost to test automation
−Integrate tests with builds