-
Notifications
You must be signed in to change notification settings - Fork 457
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
Update providers to use expect syntax #217
Conversation
Merged build triggered. (Status: PENDING, Details: null) |
Merged build started. (Status: PENDING, Details: http://box.bob.sh:8080/job/puppetlabs-firewall/315/) |
The expect syntax is much better than the should syntax and ships with RSpec 2.14. It caused a few conflicts with the mocha stubbing, so I updated the docs to use rspec test doubles instead.
Merged build triggered. (Status: PENDING, Details: null) |
Merged build finished. (Status: FAILURE, Details: http://box.bob.sh:8080/job/puppetlabs-firewall/315/) |
LGTM, particularly because it fixes the builds errors since rspec 2.14 was released. Do you know why puppetlabs_spec_helper favours mocha? Will this follow through as a recommendation to that and other puppetlabs modules that use it? |
retest this please |
Merged build triggered. (Status: PENDING, Details: null) |
Merged build started. (Status: PENDING, Details: http://box.bob.sh:8080/job/puppetlabs-firewall/320/) |
Update providers to use expect syntax
Merged build finished. (Status: SUCCESS, Details: http://box.bob.sh:8080/job/puppetlabs-firewall/320/) |
The expect syntax is much better than the should syntax and ships with RSpec 2.14. It caused a few conflicts with the mocha stubbing, so I updated the docs to use rspec test doubles instead.