Skip to main content

Conceptual Design and Controller Testing

  • Chapter
  • 941 Accesses

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.

This is a preview of subscription content, log in via an institution.

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   49.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Authors

Rights and permissions

Reprints 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

Publish with us

Policies and ethics