Jamie Cool Program Manager Microsoft

1. FT05 Automating "Done Done“ in the Team Workflows with Microsoft Visual Studio Ultimate and Team Foundation Server 2010 Brian A. Randell Senior Consultant MCW Technologies Jamie Cool Program Manager Microsoft

2. Agenda • What does it really mean to be “Done” • Going from “It Builds” to “Done” in < an hour • Automated Builds • Gated Checkins • Automated Tests • Test Lab Deployment

3. An Unfortunately Common Scenario Achieving Done only at the End • Dev writes code • Dev makes sure his component compiles • Dev checks in code • Repeat x15 devs for 4 weeks • Dev lead does a build of all components • App is installed in test environment • Test tries to test it • App doesn’t work • Dev blames test

4. Working in Cycles • Different cycles have their own “Done” • “Done” earlier is better than “Done” later Daily Build Testable Iteration Check In Story Product

5. The Tradeoffs • Deferring “Done” has costs • Low build quality during development • Finding issues late • Not knowing how much you really have left • Achieving “Done” ASAP has costs • Manual verification is expensive & error prone • Automated verification requires huge investments – often hard to win support for • Deferring “Done” is often the default choice

6. The “Done” Sweet Spotwith VS Ultimate & TFS 2010 • Automate “Done” • Provides the infrastructure for you • Focus on what’s unique for your app • Adopt one step at a time • Enforce “Done” for each cycle • Check-in Policy • Gated Check-in • Continuous Integrations • Know when you’re “Done” • Test reports • Project data reports Source Control Work Items Builds TFS Execute Tests Validate Layering Deploy Build

7. Our Scenario… • What we have… • An app • The App project builds in VS • A fully configured VS Ultimate & TFS 2010 environment • What we don’t have… • Any things else (builds, tests, setup packages) • What we are going to achieve in < an hour... • Automated builds • Validated Checkins • Automated unit & acceptance tests • Automated deployment & acceptance test verification • Reporting of “Done” metrics

8. Step 1: Automated Build • Automated builds are the pillar of “Done” • No engineering improvement gives more back • You build it all at the end, so why not build it all early • VS & TFS makes automated builds simple • Automated builds don’t have to be scary & complicated • Any project that builds in VS can have an automated build in seconds • Fully extensible • Integrated Windows Workflow engine • From a single build machine to a build lab executing a build across many machines

9. Automated Build demo

10. Step 2: Continuous Integration (CI)No more build breaks with Gated Checkin • CI let’s you continually check for regressions • Constantly run builds & assess your “Done” level • Identify problems soon after they are introduced • VS & TFS has built in support for CI • No special work required • You just need the build machine cycles • Gated Checkin guarantees no more build breaks • TFS runs a build before each check-in (synchronous CI) • Never hear “It worked on my machine” again • Guarantees no code ever gets in that doesn’t meet at least some “Done” criteria

11. Gated Checkin demo

12. Step 3: Automated Testing • Automated tests lets you stay “Done” • Don’t just get “Done”; stay “Done” • Generally the more you can automate the better • Cost of automation often means it doesn’t happen • VS lowers the barrier & cost to test automation • From unit tests to automated UI tests • Test support was a key VS 2010 investment • Integrate tests & build • Ensure your tests pass as early as possible • Get test status with every build

13. Automated Testing demo

14. Step 4: Test Lab Deployment • Being able to run the app is key to being “Done” • It’s hard to know if you’re done if you can’t use the app • Going from build to deployed app is often a barrier • Doing it for every build is a major barrier • 2010 includes virtualized lab management • Automatically spin up / tear down of lab environments • Manage machines as a group • Network isolation • Integrate builds and lab deployment • Automatically deploy builds & run tests • The app is then available for any kind of further testing

15. Traditional Workflow

16. Automated Workflow

17. Test Lab Deployment demo

18. Knowing your “Done” demo

19. Summary Lab Management • “Done” in less than an hour! • Adopt one step at a time • You don’t need to do all of this at once • You’ll see immediate payback from each step • Learn more • Try out Beta 2! • http://www.microsoft.com/visualstudio/ Gated Checkin Dashboards & Reporting Automated Build Automated Testing

20. YOUR FEEDBACK IS IMPORTANT TO US! Please fill out session evaluation forms online at MicrosoftPDC.com

21. Learn More On Channel 9 • Expand your PDC experience through Channel 9 • Explore videos, hands-on labs, sample code and demos through the new Channel 9 training courses channel9.msdn.com/learn Built by Developers for Developers….

23. Backup

24. When is Software Done? When… • the code is written (code complete)? • the code builds? • unit tests pass? • acceptance tests pass? • all of the code in the bugs are fixed? • the customer says it’s done?

25. A Desirable Development ModelAchieving Done Early & Maintaining it • Dev writes code & unit tests • Dev is only able to check in if his code builds & core tests pass • Regular automated builds happen for the entire product • Build is automatically deployed to test environment • Acceptance tests validate product quality e2e

26. Step 5: Knowing your “Done” • Know your “Done” state at any given time • State of your builds • Test results • What user stories are complete • How many bugs remain