Chef, Kitchen, rspec, PowerShell, DSC and Pester make for a power combination when used together to write tests which drive the development of your configuration code. In this talk, we will use these tools to write our infrastructure configuration code with high quality and teach you how too.

1. TDD with
Chef, DSC and Pester
on Windows

2. About Me
 Robb Schiefer
 @chief7
 Blog – dotnetcatch.com
 BHM.NET Meetup Co-founder
 10 years with EBSCO Industries, Inc.
 500+ developers
 Internal Business Systems
 100+ applications/services
 Solution Architect for 3 years
 CD – Deploy to PROD every 9 hours

3. Why use Chef? Why use TDD with Chef?
 Manual server configuration is
 Slow
 Error prone
 Inconsistent
 Manual
 Adhoc
 Chef/DSC provides
 Speed
 Consistency
 Repeatability
 Automation
 Scheduling
Test Driven Development increases velocity
and produces better designs.

4. Intro to Chef
 Infrastructure Automation via Ruby
 Benefits
 Automated/repeatable server configuration
 Avoid configuration drift
 Versioning of configuration
 Testable
 Components
 Chef Server
 Chef Client
 Cookbooks
 Recipes

5. Intro to Chef

6. Intro to Chef

7. Intro to Chef

8. Chef and Windows/DSC
 Linux supported first
 Windows support came slowly
 Meanwhile PowerShell DSC was released
 Chef added support for DSC
 Chef Server benefits
 Reporting
 Roles/Environments
 Admin UI
 Attributes

9. Chef Cookbook

10. Unit Testing – ChefSpec & rSpec
 Cookbook/recipe evaluated in ChefSpec sandbox
 Chef-Client not fully executed
 Provides
 Syntax checking for Ruby/Chef
 Verify logic in recipe
 Guards
 Expectations
 Property
 Re-evaluates cookbook for each test by default
 Berkshelf provides dependent cookbooks

11. Unit Test DEMO

12. Integration Testing - Kitchen
 Testing framework
 Create - Provisions test environment with Drivers
 Vagrant
 HyperV
 OpenStack
 AzureRM
 Converge – Applies cookbook to VM
 Verify - Executes integration tests
 InSpec
 Pester
 ServerSpec
 Destroy – Deletes test environment
Create
Converge
Verify

13. Kitchen Timings (2008R2)
 Finished creating <default-w2008r2> (2m44.22s).
 Finished converging <default-w2008r2> (4m27.82s).
 Chef Client finished, 2/4 resources updated in 01 minutes 44 seconds
 Finished converging <default-w2008r2> (0m47.00s).
 Chef Client finished, 2/5 resources updated in 16 seconds
 Finished verifying <default-w2008r2> (0m36.66s).
 Tests Passed: 2 Failed: 0 Skipped: 0 Pending: 0 Inconclusive: 0
 Roughly 10 minutes total, 60-90 sec feedback loop in DEV
 20 GB VM image

14. Kitchen Timings (Nano)
 Finished creating <acme-win-webdefault-nano> (0m35.12s).
 Finished converging <acme-win-webdefault-nano> (3m45.38s).
 Downloading/installing Chef
 Finished converging <acme-win-webdefault-nano> (0m27.71s).
 Finished verifying <acme-win-webdefault-nano> (0m9.84s).
 Roughly 5 minutes total, 30-40 sec feedback loop in DEV
 600MB VM image

15. Pester & Kitchen
 PowerShell testing framework
 Runs across WinRM on the test target
 Provides assertions, mocks, test results
 All the power of PowerShell
 Test organization

16. Kitchen DEMO

17. Setup
 OS - Windows10
 ChefDK v1.2.22
 Hyper-V
 PowerShell v5.1.14393.693
 Pester 3.4
 DSC 1.1
 Ruby Gems
 kitchen-hyperv
 kitchen-pester
Source on
http://bit.ly/tddchef

18. Troubleshooting Chef/Kitchen
 Kitchen debug info
 kitchen converge -l debug
 Verify Gem versions
 Cookbooks continually changing
 3/17 – Windows Resource 3.0
 Destroy and recreate VM
 Networking issues
 Chef on Windows Experts
 Matt Wrock - @mwrockx
 Steven Murawski - @StevenMurawski

19. Questions
Please complete your session evaluations with helpful feedback so I can
improve!
Robb Schiefer
@chief7
dotnetcatch.com