How to implement TDD in DevOps : Right and Wrong
This talk will cover the pattern of following TDD when developing using Automated Configuration Management frameworks like Chef/Puppet. Real usability of Testing is based on keeping sanctity of WHAT needs to be tested WHERE. Talk will cover the same in domain of DevOps.
This will cover the Concpetual Mapping of Unit Testing, Integration Tests and Performance Tests in reference of development under DevOps practices.
The common mistakes that used to happen in DevOps domain was direct mapping of Business Application TDD model. Like porting of Testing tools such as rspec, cucumber for DevOps utilities and blindly implementing to show 100% coverage whether the Tests were actually justified there or not.
We'll be seeing such examples and the correct way to implement justified Tests for your DevOps set-up.
Port of test packages like RSpec (puppet-rspec, chefspec) shall be used for only which cases and how they are totally un-justified for to plainly test the Resources which are just imitations without a real node.
Outline/structure of the Session
Pointing out the main process/features involved in development of Automated Configuration Management solution discussing how, where and when to Test.
I'll be covering different use-cases of Automate Configuration Management utilities (like Chef/Puppet) and mention the Wrong and Right way to Test those scenarios.
It will end with Quick Tips of WhiteList and BlackList for Testing in Auto-Config-Mgmt utilities.
Knowledge of practices to be followed for TDD in Automated Configuration Management development.
Anyone involved with DevOps practices.