Design Driven Testing: Test Smarter, Not Harder

Chapter 6. Conceptual Design and Controller Testing

As you saw in Chapter 5, unit testing doesn't have to involve exhaustively covering every single line of code, or even every single method, with tests. There's a law of diminishing returns—and increasing difficulty—as you push the code coverage percentile ever higher. By taking a step back and looking at the design on a broader scale, it's possible to pick out the key areas of code that act as input/output junctures, and focus the tests on those areas.

But what if you could take an even smarter approach? What if, rather than manually picking out the "input/output junctures" by sight, you could identify ...