RSpec 3.0.0 broke rspec-puppet unit tests
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
puppet-neutron |
Fix Released
|
Undecided
|
Sebastien Badia | ||
Havana |
Fix Committed
|
Undecided
|
Unassigned | ||
Icehouse |
Fix Released
|
Undecided
|
Unassigned | ||
puppet-openstack |
In Progress
|
Undecided
|
François Charlier |
Bug Description
Our gate installs and uses rspec-puppet which installs the rspec >= 2.9.
RSpec deprecated a bunch of stuff and broke rspec-puppet.
Example of broken jobs:
http://
RSpec::
protocol. For the current protocol you should expose the failure messages
via the `failure_message` and `failure_
The `:example_group` key in an example group's metadata hash is deprecated. Use the example group's hash directly for the computed keys and `:parent_
Using `should` from rspec-expectations' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` instead. Called from /Users/
The main issue is caused by this failure:
Failure/Error: expect(
expected false to respond to `false?`
A change was brought in RSpec 3.0.0 related to built-in matchers (thanks Sebastian Badia for those links):
Rename be_true and be_false to be_truthy and be_falsey. (Sam Phippen)
References:
* https:/
* https:/
Related issues in rspec-puppet project:
* https:/
* https:/
* https:/
* https:/
description: | updated |
description: | updated |
Changed in puppet-openstack: | |
assignee: | Sebastien Badia (sbadia) → François Charlier (francois-charlier) |
Fix proposed to branch: master /review. openstack. org/97559
Review: https:/