Working with unit tests and CI in a team environment poses some interesting process challenges. It's good to enforce the stigma of the Broken Build, but process should help prevent that scenario from ever occurring in the first place (disclaimer: I've been party to responsibility for broken builds twice in two days, ashamedly).
I'm thinking the following process should be enforced:
- Write Tests (TDD & all)
- Write Code to pass Tests
- Refactor
- Make sure Code passes Tests
- [placeholder -- ready for checkin] Prepare for checkin by:
- Update code (get latest)
- Build
- Run All Tests
- Refactor as needed
- Checkin Code
If this process is not used, there's a more serious concern of regression tests only getting caught at the automated CI build, rather than through the everyday making sure that tests are going to pass proactively prior to actually submitting code to the source engine.