>>> Using your sample project, if I include the puppetlabs_spec_helper in the >>> Gemfile, it doesn't error but completes rather quickly saying there are no >>> tests (obviously). But it doesn't bawk on any ec2 configuration. >> >> So puppetlabs_spec_helper assists with the unit testing side of things >> and has nothing directly to do with beaker, so look into rspec-puppet >> for the long story around that. puppetlabs_spec_helper provides a >> number of utilities and helps bridge the testing parts with various >> different versions of puppet basically, but the main piece of work >> that users should focus on is rspec-puppet. >> >> Basically from a user perspective the helper gives you a rake task: >> `rake spec` and a file like so: >> https://github.com/puppetlabs/puppetlabs-puppetdb/blob/master/.fixtures.yml >> that will help you automatically retrieve the other modules your >> module depends on during testing time. As opposed to just running >> `rspec spec/unit` for example. So yeah, chalk and cheese ... > > Hmmm. I'm pretty sure the puppelabs_spec_helper gave me a beaker target....
Yep you are right, it was added in January by blkperl. I didn't realize this. So in response to your original question: >>> Using your sample project, if I include the puppetlabs_spec_helper in the >>> Gemfile, it doesn't error but completes rather quickly saying there are no >>> tests (obviously). But it doesn't bawk on any ec2 configuration. Perhaps its because its using the `default.yml` definition that it is not complaining. Perhaps that AMI is public and fine. Check `spec/acceptance/nodesets/default.yml` in your project for what this contains. All the rake task seems to do is run beaker with --color and the spec/acceptance directory as a path, so beakers defaults everywhere else kick in. Which makes sense, in this case there are several BEAKER_* style variables that are used to setup the details in CI for example. This is because CI software such as Jenkins uses environment variables as a primary API between the Jenkins job data and the jobs scripts being executed. https://github.com/puppetlabs/beaker/wiki/How-to-Write-a-Beaker-Test-for-a-Module The BEAKER_set allows for a basic way of executing a particular nodeset for example, which is rather nice. Perfect for a matrix job in Jenkins to iterate across your distros. ken. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE4bNT%3DPeu-CEU50yFTgoyWhywHAPbqz6tbD_PVTKznv-FDPqw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
