Chapter 4. Examining software tests

This chapter covers

  • The need for unit tests

  • Understanding the different types of tests

  • Test coverage: how much is enough?

  • Practicing Test-Driven Development

  • Testing in the development cycle

 

A crash is when your competitor’s program dies. When your program dies, it is an ‘idiosyncrasy’. Frequently, crashes are followed with a message like ‘ID 02’. ‘ID’ is an abbreviation for idiosyncrasy and the number that follows indicates how many more months of testing the product should have had.

 
 --Guy Kawasaki

Earlier chapters in this book took a very pragmatic approach to designing and deploying unit tests. This chapter steps back and looks at the various types of software tests, the role they play in the application’s life ...

Get JUnit in Action now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.