Test Driven Development for Embedded C

Test Disrespect Antipattern

In teams new to TDD, not all team members will have bought into doing the tests. Those resisting TDD and unit testing exhibit Test Disrespect. This behavioral antipattern works like this: you develop functionality using TDD and make it part of the continuous integration build. A teammate makes a change, manually tests it, and checks in their work. Little did they know that their work broke your prior work, but the CI system does not rest. It lets all know about the broken build.

If the respect is low enough, your teammate (if you can call him that after this next move) deletes the rightfully whining test cases. His stuff works after all—he tested it. A less disrespectful teammate just put the tests in IGNORE_TEST ...