Check in dance

2,129 views

Published on

Introduction to Continuous Integration. Combining with Acceptance Test Driven Development, Test Driven Development, Showing how a developer in agile team does the work.

Published in: Technology
1 Comment
3 Likes
Statistics
Notes
No Downloads
Views
Total views
2,129
On SlideShare
0
From Embeds
0
Number of Embeds
310
Actions
Shares
0
Downloads
57
Comments
1
Likes
3
Embeds 0
No embeds

No notes for slide

Check in dance

  1. 1. Daniel Teng, Certified Scrum Coach Tech talk at Think in Lamp Gathering June 6, 2010
  2. 2.  Continuous Integration  Check In Dance  ATDD & TDD  Live Demo
  3. 3.  The Challenges  CI in One Page  Why It Helps  Visualize the Status  CI Tools  Basic Guidelines
  4. 4.  Integration of components  Application configuration  Deployment  Testing  Monitoring  Logging
  5. 5.  Safe Net  Communication  Feedback  History
  6. 6.  Website  Email  Desktop notification  Build monitor  Traffic light  Rabbit  Sound
  7. 7.  Hudson  CruiseControl, CruiseControl.Net, CruiseControl.rb  TeamCity  Team Foundation Server  More on http://en.wikipedia.org/wiki/Continuous_Integ ration#Software
  8. 8.  Check in as often as you can  Avoid stale code  Don't ever check into or out of a busted build  Communicate and negotiate check in's to the rest of the team  If you're working on fixing the build, let the rest of the team know  DON'T LEAVE THE BUILD BROKEN OVERNIGHT
  9. 9.  Check in Dance  Go
  10. 10.  Get the latest code from source control.  Do a merge on any conflicts.  Run the build locally and fix any problems  Peer Review  Let the rest of the team know a change is coming if it's a significant update.  Commit the changes to source control.  Stop coding until the build passes.  If the build breaks, drop everything else and fix the build.
  11. 11.  The Agile Cycles  TDD Cycles
  12. 12. Sprint demo Acceptance Test Continuous integration Unit test Pair programming
  13. 13. User Story Selected For Development Iteration Story Implemented Domain Model / User Using TDD Story Elaborated For Feature Unit Tests StoryTest developed by Initially Fail Business Owners and Development/QA Refactor Until Unit Tests Story StoryTest Initially Pass Accepted Fails when Story Test passes Defining “done” for a user story.
  14. 14.  Problem -> String Calculator  Tools  Fitness & Slim, FitSharp (revised)  TeamCity  C# 3.5  VS.Net 2008 + ReSharper 4.5  SubVersion  NAnt + MSBuild  NUnit  NCover + NCoverExplorer  NDepend
  15. 15. Email: tengzhenyu@gmail.com Blog: http://www.cnblogs.com/tengzy/ LinkedIn: http://www.linkedin.com/in/dteng Twitter: http://twitter.com/danielteng

×