JavaZone 2010 - Mocking too close for comfort?
One of the issues with TDD and using mock objects is the high amount of code mirroring between the unit test code and the code under test. This duplication have some bad sideeffects:
- Tests become brittle - later changes in the implementation may break them.
- Tests become extremely verbose and can be hard to follow
- Refactoring the tests may become difficult
This lightning talk is focused on giving developers some solutions to this problem.
Thomas Arp
Consultant at Bekk Consulting.
System developer with years of experience with developing web and mobile applications in Java.