Infrastructure as Code, 3rd Edition

Chapter 15. Approaches for Testing Infrastructure Code

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles. This will be the 15th chapter of the final book. Please note that the GitHub repo will be made active later on. If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

TODO

Consider chapter sequencing to clarify the relationship between this chapter and [Link to Come].

Some code (or pseudo-code) examples of different types of tests, e.g. static analysis, stack tests, integration tests.

Look at https://github.com/sigstore/cosign, https://github.com/sigstore/sigstore or https://in-toto.io/)

Continuously testing and delivering changes to infrastructure code is the second of the three core practices of Infrastructure as Code that I described in Chapter 1 (“Core Practices for Infrastructure as Code”), along with defining everything as code and building infrastructure from small, simple pieces.

If a strong focus on testing creates good results when writing application code, it’s reasonable to expect it to be useful for infrastructure code as well. This chapter explores challenges and approaches with testing infrastructure code. It draws heavily ...