Any developer who cares about software quality should be committed to writing unit tests. Used well it can be a vital tool in every developer’s toolbox, but unfortunately the theory and practice don’t always match up. Easily-made mistakes can lead to brittle, unmaintainable and ‘write-only’ tests that not only become difficult to work on, but can lead to a hatred of unit testing in general. Presented here are examples of these mistakes with code samples, why you’re making them and how to avoid them in future.
Java engineer, technology evangelist @ Shazam, TDD zealot, cyclist bio from Twitter
Sign in to add slides, notes or videos to this session