Beaker is a test harness focused on acceptance testing via interactions between multiple (virtual) machines. It provides platform abstraction between different Systems Under Test (SUTs), and it can also be used as a virtual machine provisioner - setting up machines, running any commands on those machines, and then exiting.
Beaker runs tests written in Ruby, and provides additional Domain-Specific Language (DSL) methods. This gives you access to all standard Ruby along with acceptance testing specific commands.
See Beaker Installation.
Documentation for Beaker can be found in this repository in the docs/ folder.
Table of Contents
- Tutorials take you by the hand through the steps to setup a beaker run. Start here if you’re new to Beaker or test development.
- Concepts discuss key topics and concepts at a fairly high level and provide useful background information and explanation.
- Rubydocs contains the technical reference for APIs and other aspects of Beaker. They describe how it works and how to use it but assume that you have a basic understanding of key concepts.
- How-to guides are recipes. They guide you through the steps involved in addressing key problems and use-cases. They are more advanced than tutorials and assume some knowledge of how Beaker works.
Beaker functionality has been extended through the use of libraries available as gems. See the complete list for available gems. See the beaker-template documentation for documentation on creating beaker-libraries.
Support & Issues
Please log tickets and issues at our Beaker Issue Tracker. In addition there is an active #puppet-dev channel on Freenode.
If you'd like to contribute improvements to Beaker, please see CONTRIBUTING.
For information on project maintainers, please check out our CODEOWNERS doc.
This plugin was originally authored by Puppet Inc. The maintainer preferred that Puppet Community take ownership of the module for future improvement and maintenance. Existing pull requests and issues were transferred over, please fork and continue to contribute here.
This gem is licensed under the Apache-2 license.
To make a new release, please do:
- update the version in the gemspec file
- Install gems with
bundle install --with release --path .vendor
- generate the changelog with
bundle exec rake changelog
- Check if the new version matches the closed issues/PRs in the changelog
- Create a PR with it
- After it got merged, push a tag. GitHub actions will do the actual release to rubygems and GitHub Packages