Summary

In this chapter, you learned how to use several of the tools available to implement a test-driven development cycle for infrastructure code development. We looked at tools that focus on cookbooks-as-code, validating that the code is syntactically correct, that it is structurally correct, and that it follows the coding standards we want all of our source code to employ. These tools include RuboCop and Foodcritic. Then, we looked at tools that fit into the cookbooks-as-artifacts model and test the functionality and deployment aspects of our cookbooks. These tools include ChefSpec and Test Kitchen. We learned that when tests are performed on our cookbooks in both models, the result is better infrastructure delivered faster than ever before. Remember that what you learned in this chapter is only the beginning. In fact, we barely scratched the surface. It is up to you, the reader, to persist in your education and the use of these test tools. Continue to the point where your normal workflow...