-
Notifications
You must be signed in to change notification settings - Fork 49
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
Test fixes #84
base: master
Are you sure you want to change the base?
Test fixes #84
Conversation
It keeps failing on the rbx build. Will investigate this further. |
@magicalbanana Did you get any further with the failing rbx builds? I could take a look at it sometime this week if that's any help? @ConradIrwin Can we push for a new release if the tests above pass on rbx? This is currently holding up a release of pry. See pry/pry#1448 for more information. |
@unfunco never did. Did not find time, but maybe next week or so I can build a box that has rbx built in it and try and see if I can fix it. |
I think we should just drop support for rbx. |
begin | ||
b1 = binding | ||
raise "original" | ||
rescue => e1 | ||
rescue => ErrorOne |
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.
@magicalbanana This creates a new global constant, which you almost certainly don't want to do (it will leak between tests). If you need to extend the scope of the variable use a local that's set to nil at the start of the test. Same applies everywhere you are rescuing into a constant.
Happy to drop Sorry for the long lead time on this. |
Yeah, thanks for dropping rbx. It would be better if we did, I mean I really do not know anyone who uses rbx, would've been nice if we could make it work though. |
Can this still be used? I see some stuff that might be useful here |
Fixed the failing error test. I believe it's best to create the modules for raising exceptions outside and calling them. Will probably do that later on.
Also since the RSpec dependency is not restricted to a version I updated the syntax of the test to match the RSpec 3+ syntax methods.
All tests pass, the only thing that was really changed or modified to pass was the commands_spec.rb.