-
Notifications
You must be signed in to change notification settings - Fork 202
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
Rspec 3 and 2 compatibility #225
Conversation
…ec3_test Conflicts: lib/rspec-puppet/matchers/run.rb
…ec3_test Conflicts: lib/rspec-puppet/matchers/run.rb
@@ -12,7 +12,7 @@ module ManifestMatchers | |||
"include Class[#{expected_class}]" | |||
end | |||
|
|||
failure_message_for_should do |actual| | |||
failure_message do |actual| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll probably need to alias failure_message to failure_message_for_should here
move the rspec2 catcher to support.rb
- add newer ruby version - add new puppet version - add rspec2 - exclude new puppet on old ruby
Looks good to me 👍 Any progress on getting this merged and shipped? I'm starting a new module and would love to start the test suite off against RSpec 3 and save the pain of an upgrade down the road. |
@rodjek I have finished the work on rspec2/3 compatibility and have added some more tests. Please let me know whether you see stuff which needs to get changed. |
Remove deprecation warnings on
But still keeping RSpec 2 functional