Before starting - Do you follow a Test Driven Process?
Last updated by Brady Stroud [SSW] 7 months ago.See historyNever allow a situation where a developer can check outcode and the code does not compile – or the unit tests are not all green. This is called “breaking the build” and the punishment in our office is 20 push-ups and fixing broken links for an hour!
- Check out
- Compile
- Develop
- Compile
- Check-In
Figure: Bad example - wrong process
- Get latest
- Compile
- Run Unit Tests
- If Tests pass then start developing
- Check out
- Develop
- Compile
- Run Unit Tests
- Get Latest (Always do a Get Latest before checking in as code you didn't change could break your code)
- Compile
- Run Unit Tests
- Check-In if all tests passed
- Wait for gated check-in (GC) to complete
- Reconcile your workspace if it was successful
- Check that Continuous Integration (CI) build was successful(If GC was skipped)
Figure: Good example - right process ** **
Note: You should have both a Gated-Check-in (GC) and a Continuous Integration (CI) build on every branch.