Skip to main content
  • 2488 Accesses

Abstract

Agile development focuses on catching bugs as soon as they are introduced. Optimally, the bugs are caught before changes are checked in, but there are classes of bugs that are expensive for the developer to verify. They happen infrequently, they are hassle to check for, and they can be painful to track down. The most visible relate to integration, platform dependencies, and external package dependencies.

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

Access this chapter

eBook
USD 16.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 44.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 Jeff Younker

About this chapter

Cite this chapter

(2008). A Build for Every Check-In. In: Foundations of Agile Python Development. Apress. https://doi.org/10.1007/978-1-4302-0635-4_5

Download citation

Publish with us

Policies and ethics