-
Notifications
You must be signed in to change notification settings - Fork 33
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
Spec don't pass on MacOS #60
Comments
You'll probably have to use an old version of rspec. PR's are always
welcome :)
…On Wed, May 4, 2022 at 8:26 PM Peter Boling ***@***.***> wrote:
Problem
Errors:
An error occurred while loading ./spec/os_spec.rb.
Failure/Error: config.expect_with :rspec, :stdlib # enable `should` OR `assert`
ArgumentError:
:stdlib is not supported
# ./spec/spec_helper.rb:8:in `block in <top (required)>'
# ./spec/spec_helper.rb:7:in `<top (required)>'
# ./spec/os_spec.rb:1:in `require'
# ./spec/os_spec.rb:1:in `<top (required)>'
An error occurred while loading ./spec/osx_spec.rb.
Failure/Error: config.expect_with :rspec, :stdlib # enable `should` OR `assert`
ArgumentError:
:stdlib is not supported
# ./spec/spec_helper.rb:8:in `block in <top (required)>'
# ./spec/spec_helper.rb:7:in `<top (required)>'
# ./spec/osx_spec.rb:1:in `require'
# ./spec/osx_spec.rb:1:in `<top (required)>'
Warnings:
Deprecation Warnings:
Requiring `rspec/autorun` when running RSpec via the `rspec` command is deprecated. Called from /Users/pboling/src/my/moss/spec/spec_helper.rb:5:in `require'.
Solution
Use modern RSpec patterns
—
Reply to this email directly, view it on GitHub
<#60>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAADBUAUNBSDMBB2GFUA2LDVIMWURANCNFSM5VDXHQCA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Changing the focus of this issue to "Specs don't pass on MacOS".
The previous issue related to upgrading to RSpec 3 will be in #67
The text was updated successfully, but these errors were encountered: