I've said this before, but: "Emissions test driven development" http://www.nytimes.com/2016/04/27/business/international/vw-presentation-in-06-showed-how-to-foil-emissions-tests.html?smid=tw-nytimes&smtyp=cur …
-
More generally, this is what happens when you have adversarial TDD; when the tests and the code are written by people with conflicting goals
We tried adversarial TDD at work once, as an exercise. One person writes one test, the other writes the minimum of code to make it pass
-
-
We discovered that if e.g. the first test case expects a method to return 1, the first implementation of the method will return 1 every time
-
If the second test case expects 2, the implementation will simply be revised to return 1 and 2 alternately.
- 13 more replies
New conversation -
-
-
@qntm Does anybody endorse an adversarial approach? Or did you just do it to see what would happen? -
@lhochstein The purpose of the exercise was to demonstrate the importance of communication between dev and tester. Shared goal. No fences - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.