Skip to main content

Specification by Example

  • Chapter
DevOps for Developers

Abstract

One of the fundamental principles of DevOps is that any build that successfully passes the gauntlet of automated checks can potentially be delivered into production. Checks can specifically verify whether any new or updated code broke any existing feature. In other words, they guard against regression failures. It is for this reason that automated testing plays such a vital role in the DevOps process.

48% of devops are automate their test. 12% are test their automation. 3% are do both. —DevOps Borat 1

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 16.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.

References

  1. See Gojko Adzik, Specification by Example (Manning, 2011).

    Google Scholar 

Download references

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2012 Michael Hüttermann

About this chapter

Cite this chapter

Hüttermann, M. (2012). Specification by Example. In: DevOps for Developers. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-4570-4_10

Download citation

Publish with us

Policies and ethics