Automated testing best practices: insights from Puppetize PDX

See more posts about: Events and Tips & How To

Testing is a critical part of the handoff between development and IT operations. Successful DevOps teams fully integrate testing into their software development lifecycle. This creates confidence that everything will work as it should when the code is pushed to production, and reduces the risk of introducing bugs and vulnerabilities that can expose your organization to risk.

In fact, testing has a number of uses: from development, where it can be used to gain insight into the impact of changes and explore special cases, to documenting edge cases and their behavior, to building shared confidence in the code base. Successful IT organizations include a fully automated test harness that can signal to both development and IT operations teams when code that’s in development and code on running systems is passing (or failing) their tests.

Testing is also an increasingly important part of module development here at Puppet. It helps avoid regressions and support a wide range of Puppet and operating system versions. By making testing an integral part of your toolchain, the code you deliver quickly will be of much higher quality and will be more likely to work as designed.

In this collection of sessions from our user conference, Puppetize PDX, speakers share insights on the importance of automated testing and ways to make it easier.

Automated testing the easy way

Check out this video to learn how you can test all of your code without writing any actual tests using Onceover. Dylan Ratcliffe, senior professional services engineer at Puppet, covers how to get 100% test coverage over your Puppet code with very little effort and no coding required, regardless of whether you are just starting out or have so much code you’ve given up on testing it all.

Multi-node acceptance tests for fun and profit

Trevor Vaughan, VP of engineering at Onyx Point and long-time Puppet Community member, walks through the mysterious task of getting Beaker running in Puppet Development Kit and presents a multi-node acceptance test using the puppetlabs-ntp module. He also explains the importance of acceptance testing and multi-node acceptance tests.

Continuous Delivery for Puppet Enterprise: design and roadmap

Cat Rayburn, senior user experience designer at Puppet, and Carl Caum, senior product manager at Puppet, discuss the challenges IT organizations face when accelerating their velocity and coordinating across teams, all while trying to keep the lights on. They share how Continuous Delivery for Puppet Enterprise helps address these challenges, and provide a glimpse of upcoming features in our infrastructure continuous delivery solution.

Puppet sites use proprietary and third-party cookies. By using our sites, you agree to our cookie policy.