You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since upgrading to 1.0.1, some tests that used in 0.1.6 that don't pass now. Mostly, they appear to be related to tests of functions that pass either nil, :undef or '', but there's some tests do pass that pass one of those three parameters as the only parameter.
In addition (and possibly related), there's some error text being interwoven with the normal output indicating RSpec isn't happy with one of the matchers.
Here's an example:
Failures:
1) format_action => Pass nil should When you call a matcher in an example without a String, like this:
specify { object.should matcher }
or this:
it { should matcher }
RSpec expects the matcher to have a #description method. You should either
add a String to the example this matcher is being used in, or give it a
description method. Then you won't have to suffer this lengthy warning again.
Failure/Error: should run.with_params(nil).and_raise_error(Puppet::ParseError)
ArgumentError:
wrong number of arguments (0 for 1)
# ./spec/functions/format_action_spec.rb:22
Here's the spec test itself:
describe 'format_action' do
...
context '=> Pass nil' do
it {
should run.with_params(nil).and_raise_error(Puppet::ParseError)
}
end
...
end
Since upgrading to 1.0.1, some tests that used in 0.1.6 that don't pass now. Mostly, they appear to be related to tests of functions that pass either
nil
,:undef
or''
, but there's some tests do pass that pass one of those three parameters as the only parameter.In addition (and possibly related), there's some error text being interwoven with the normal output indicating RSpec isn't happy with one of the matchers.
Here's an example:
Here's the spec test itself:
Here's a gist with the entire rspec run output
The text was updated successfully, but these errors were encountered: