Closed jgebal closed 8 years ago
@javornikolov any concerns/comments on this change?
I think --requrie
option was introduced with rspec 3.x (and perhaps the transitional 2.99 version too). So I'm wondering whether we should do something to keep things compatible.
Good spot. I did not check before. The --require option was included since 2.14 What is the policy for backward compatibility in this project? Do you think it would be worth/advisable to use the most recent features of underlying libraries, even if it means bumping the project version by a number to indicate it's no longer backward-compatible?
@javornikolov I've added fixes and a test for new file.
Good spot. I did not check before. The --require option was included since 2.14 What is the policy for backward compatibility in this project? Do you think it would be worth/advisable to use the most recent features of underlying libraries, even if it means bumping the project version by a number to indicate it's no longer backward-compatible?
I think there is no strict policy for backward compatibility. It may be tricky - depends on users' environments.
But to be honest - in this case:
expect
syntax which is not available in rspec 2 (so it anyway needs some tweaking to adapt to older versions). But these are just examplesAlso I think rspec < 2.4 is not working with latest ruby.
So I guess we're not breaking anything significant by this change.
All test were passing after my latest fix. Do you think it's worth merging? I have a backlog of small tweaks and extensions, so few pull requests might be coming soon.
:shipit: Merging... @jgebal , thank you for adding this enhancement!
Thanks. It's a pleasure.
Call to plsql-spec init now creates additional file: .rspec in the project root directory.
The file contains a require, so the spec_helper is always required. This way when writing tests, the spec helper no longer needs to be explicitly required.