-
-
Notifications
You must be signed in to change notification settings - Fork 881
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
acceptance tests with new(ish) Beaker version #882
Comments
From the beaker issue, looks like you can just replace That appears in two files, I wonder how long they've been broken for... the acceptance tests need a lot of TLC because I don't think anyone's run them since I wrote them :( |
@3flex: Am I missing it in |
So, I made those changes (#883), but still getting this error (it's odd, because it seems to be in the Also, presumably we should peg the Beaker version in the Gemfile, but right now it's done in this way, not sure how to simplify that, but maybe should just peg to beaker version >
Traceback:
Also, to get them running in Travis, do we need it setup to do Docker? |
I don't think these will run as is on Travis, because they currently use Vagrant for tests. Best would be to add Docker support in voxpupuli/modulesync_configs repo, probably based on Puppet's work (puppetlabs/modulesync_configs#58), and then leverage that for this module's acceptance tests. puppetlabs-apache module has working Docker tests in Travis running under Beaker, might be worth poking around their repo to see how it's configured. That would be a huge win. Allows other cool stuff like possibly integrating https://github.com/ssllabs/ssllabs-scan to automatically test default configuration for broken SSL settings. |
It's definitely the #883 fixes the problem for me but, I still haven't addressed the requirement of beaker-rspec version in the Gemfile... can someone with more Ruby experience than me suggest how to change the existing code in and around: |
I think the Gemfile looks good already, since as you said when you opened this issue if you set the To your point, yes, this probably should default to a known-good beaker version so people can easily run tests on their own machines, but I think the defaults around system tests in the Gemfile are designed to back testing on Travis rather than testing on their own boxes. I also think the intention would be to have the tests successfully run on the latest beaker version rather than pinning to an older version. I might be wrong about this, I'd suggest asking on IRC or Slack about the intentions behind it, but IMHO the current Gemfile is adequate. |
…_tests Fix acceptance test failures with newer Beaker versions Fixes voxpupuli#882
How to reproduce (e.g Puppet code you use)
run
bundle exec rake acceptance
What are you seeing
/usr/local/lib/ruby/gems/2.3.0/gems/beaker-2.51.0/lib/beaker/dsl/helpers/host_helpers.rb:81:in
block in on': DSL methodon
can only be called with a String or Beaker::Command object as the command parameter, not NilClass. (ArgumentError)`What behaviour did you expect instead
acceptance tests to run
Output log
Any additional information you'd like to impart
I set export
BEAKER_VERSION=2.32.1
and ranbundle update beaker
, and this seemed to fix it.Maybe related to:
https://tickets.puppetlabs.com/browse/BKR-716
but not knowledgeable enough in this area to figure out exactly what changes or what combination of deps would allow this to work on a newer beaker version.
The text was updated successfully, but these errors were encountered: