Abstract
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.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2010 Matt Stephens, Doug Rosenberg
About this chapter
Cite this chapter
Stephens, M., Rosenberg, D. (2010). Conceptual Design and Controller Testing. In: Design Driven Testing. Apress. https://doi.org/10.1007/978-1-4302-2944-5_6
Download citation
DOI: https://doi.org/10.1007/978-1-4302-2944-5_6
Publisher Name: Apress
Print ISBN: 978-1-4302-2943-8
Online ISBN: 978-1-4302-2944-5
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books