{"id":347,"date":"2016-04-14T09:45:00","date_gmt":"2016-04-14T09:45:00","guid":{"rendered":"https:\/\/opstree.com\/blog\/\/2016\/04\/14\/chef-kitchen-do-it-simply\/"},"modified":"2026-01-05T14:42:35","modified_gmt":"2026-01-05T09:12:35","slug":"chef-kitchen-do-it-simply","status":"publish","type":"post","link":"https:\/\/opstree.com\/blog\/2016\/04\/14\/chef-kitchen-do-it-simply\/","title":{"rendered":"Chef-Kitchen Do it simply.."},"content":{"rendered":"
\r\n
\r\n
\u00a0<\/div>\r\n
<\/div>\r\n

\u00a0<\/h2>\r\n
If you are from agile background you would be already aware about the importance of testing your code as you develop. As DevOps SCM tools are maturing where we try to have our complete infrastructure as code it becomes a dire necessity to have our infrastructure code to be tested as well. In this blog I’ll showcase how I’m using the testing capability of Chef to test our Chef code.<\/div>\r\n

Prerequisites<\/h2>\r\n
This blog assumes that you have a basic understanding of Chef, Docker, Git and Vagrant. This blog is written in consideration with centos as platform. You can follow same procedure for ubuntu with some basic changes.<\/div>\r\n
\u00a0<\/b><\/div>\r\n
Setup Kitchen<\/div>\r\n
Clone from our github repository to spin up a vagrant with kitchen and other chef tools.<\/div>\r\n
\u00a0<\/b><\/div>\r\n
$ git clone git@github.com:OpsTree\/Chef.git<\/div>\r\n
\u00a0<\/b><\/div>\r\n