-
Notifications
You must be signed in to change notification settings - Fork 727
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
Using fluent syntax unintentionally removed in 3.8 #2412
Comments
Before implementing a solution to this I think we should have tests that cover all the functionality of CollectionContainsConstraint - as it were in version 3.7 - and then use these tests to ensure that we have kept all the behaviour. I'll try to look into writing these tests tonight (if I have time). The tests should also cover #2411. |
I updated the title of this issue to better reflect what it is. Feel free to reword if needed. I think this could warrant another hotfix since I don't think there is a workaround. There is a hotfix for #2411, but we could include it if this one is going out. As for unit tests, we have tons of syntax tests and constraints tests, but we lack many tests that purposefully chain constraints together. I was thinking we should add a series of fluent syntax tests that do just that. They could be simplistic tests that just set up what we know is passing data and exercise various combinations of constraints. |
@rprouse I think we once had a test that covered almost all the syntax, including chaining things together. We may have eliminated it at some point in favor of more targeted tests. If so, it seems like that wasn't such a good idea. 😞 I'll take a look. |
I've tried to go through all the changes done in #2239 and write tests for each change. All the tests pass in version 3.7.1, but in 3.8.1:
https://gist.github.com/mikkelbu/370fe6a735c41906dca1fad28282f19e |
That test file looks great Mikkel. 👍 I'm surprised there was so much missing from our test suite. 😞 |
@nunit/framework-and-engine-team I've assigned this issue and #2411 to myself, and I have a technical question (or two).
|
@mikkelbu you can base your changes on the master branch. I can cherry-pick the changes for the release. It would be easier to fix both issues in one PR since they are related. It will also make cherry picking the changes easier. Don't worry about updating CHANGES.md or the version number, I do that as part of the hotfix. |
@rprouse I've added this issue to the 3.8.2 milestone. |
This change was unintentional - the removal of CollectionContainsConstraint wasn't intended to cause any breaking changes.
@mikkelbu did the below analysis of what happened:
@rprouse - will leave you to decide if this should be critical or not, possibly along with #2411 - I haven't looked into that one.
The text was updated successfully, but these errors were encountered: