-
-
Notifications
You must be signed in to change notification settings - Fork 765
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
config.include works unpredictably when supplying more than one metadata to filter #3080
Comments
This would be a breaking change, and we plan to release all this in RSpec 4. I kindly appreciate it if you could check if the code on 4.0-dev branch meets your expectations. The branch is behind our main branch and may miss some latest fixes. Please let me know if it doesn’t work properly, it will be a good motivation to forward-port fixes to it. |
I've tested 4-0-dev against the inline code and it passes. 🎉 FYI using
So that's wonderful! Also tested rspec 4 on a rails project with a decent number of tests and all ran fine (after adapting to rspec 4 changes). @pirj Had no idea about RSpec 4.0 -- so much great work, and yet seemingly still so far away (looking at rspec/rspec-metagem#61). Yet looks like the main thing to complete on the 4.0 list is testing (there's also a post-4.0 list and a cleanup list - but are those optional?) |
Awesome! Thanks for checking this. Almost there actually. We wanted to glue all repos together into one repo. It would allow to shuffle things between repos, simplify our builds, and simplify cross-gem fixes. but it’s tricky and time-consuming with all those tags and branches. |
4.0 is mostly waiting on me to finish the monorepo setup and prepare the release from existing work, plus any preparatory work for 3.99 I hope to get back to this soon. I'm going to close this as 4.0 seems to fix your issue and it would be a breaking change to fix it any earlier |
Subject of the issue
When supplying more than one metadata to filter for config.before or config.include, I would expect them both to:
config.before
andconfig.include
behave differently)config.before
works like this, butconfig.include
seems to just requires any of the metadata to be present)Or have I missed some docs where it says don't use more than one metadata to filter on?
Your environment
Steps to reproduce
inline ruby
Expected behavior
No failures.
Actual behavior
3 failures
output of running above code
The text was updated successfully, but these errors were encountered: