Skip to main content
  • 442 Accesses

Abstract

Untested code has the potential to contain errors and bugs. Whether caused by an invalid assumption, an explicit coding mistake, or an otherwise-unknown issue, bugs that appear in code cause problems. Developers lose time trying to find such mistakes, organizations lose productivity, and companies lose money. For more critical systems, human lives can be lost if a software glitch occurs. This is why developers test code.

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

Access this chapter

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

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Rights and permissions

Reprints and permissions

Copyright information

© 2008 Adam Myatt

About this chapter

Cite this chapter

(2008). JUnit Testing. In: Pro NetBeans™ IDE 6 Rich Client Platform Edition. Apress. https://doi.org/10.1007/978-1-4302-0439-8_9

Download citation

Publish with us

Policies and ethics