Back to proposals-2013
Title: Beyond mocking - Sustainable unit testing
Proposer: gil_zilberfeld
Type: Tutorial
Duration: 90 minutes
Description:
When you start your path in unit testing you start with selecting a test framework, and usually the next stop is a mocking framework. You tool belt is equipped.
You’re covered, right?
If you search for unit testing resources it looks like it is a solved problem. Once you got the tools, 100% coverage is not only possible, it’s expected. But we see that even with the best tools, people still fail at their unit testing implementation. For a solved problem, it’s still not much of a solution.
This tutorial exposes the problems that don’t have a clear-cut solution; The problems that tools don’t solve. Fortunately, practices can help. These are the practices that teams have learned on their own.
We’ll discuss how to make sure we’re testing the right thing. Is TDD always the best way to go. Deal with actual legacy code, including refactoring patterns that help us a lot over time. How to use coverage reports effectively. How to review tests and what to look for.
Usually you don’t see examples like that in blogs or books, because they are complex. We’ll work on real code just because of that.
At the end of the session, you’ll feel two things: Unit testing is not a solved problem. And you know what to do to make it a sustainable process.
[YES. A rich topic to explore. Ewan]
Roger: Yes - but does it overlap too much with Seb's “Bad test, good test” ?
Asti: I don't see too much overlap with Seb although the potential is there so if we take both then we need to demarcate the topic between them
2013:beyond_mocking-sustainable_unit_testing
2013/beyond_mocking-sustainable_unit_testing.txt · Last modified: 2016/06/11 14:05 by 127.0.0.1