-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
Updates for RSpec 3 #3265
Updates for RSpec 3 #3265
Conversation
great, was hoping to have it on jruby-1_7 but I guess it won't work in --1.8 ;( mode ... thus 9K it is! |
changing |
6f54606
to
a79a887
Compare
Of course now having upgraded to RSpec 3 there are other failures. I'll get those sorted now - they seem to be mostly around the |
1bf0d71
to
46b8340
Compare
It seems those outstanding CI issues are unrelated to my changes, so I think this is good to go otherwise. I'll squish it down to something sensible when I get the OK. |
@kares thanks for reviewing 😍 Those issues should be addressed now. |
Mostly simple syntax changes to the new `expect` style but also various manual fixes where transpec didn't quite do the job. Normally around the new `pending` semantics, and that the block form of `pending` is deprecated. Another big one was being explicit about the types of errors thrown. There is still plenty of room for improvement here but at least we are up and running on the latest/greatest RSpec vintage.
@kares I rebased and squashed into one logical commit. 🚢 |
the spec ci run finished green so no need to wait for osgi++ to finish....thanks @benlovell this is massive! |
Updates JI integration specs to RSpec 3 syntax. This was performed mostly via
transpec
but did require a modicum of manual fixups. Some of the key gotchas were around the semantics ofpending
andskip
- especially the block form ofpending
which has since been deprecated. Theraise_error
matcher now requires an explicit error to reduce false-positives.I made a few other minor cleanups and there were some flat-out broken specs that were fixed too.
There is still plenty of room for improvement in the tests that I'll be happy to soldier on with.
The history isn't the cleanest so I'll squash this down to something sane once it's green but it should be good to go otherwise. ❤️