Introduction to Continuous Integration. Combining with Acceptance Test Driven Development, Test Driven Development, Showing how a developer in agile team does the work.
12. Hudson
CruiseControl, CruiseControl.Net,
CruiseControl.rb
TeamCity
Team Foundation Server
More on
http://en.wikipedia.org/wiki/Continuous_Integ
ration#Software
13. 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
15. 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.
19. 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.