Migrate NUnit assertions to the constraint model in preparation of the NUnit 4 upgrade #729
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cquirosj
force-pushed
the
nunit-assertions-migration
branch
2 times, most recently
from
b42b5e5
to
28a443e
Compare
cquirosj
force-pushed
the
nunit-assertions-migration
branch
from
28a443e
to
b76fba8
Compare
danielmarbach
approved these changes
Aug 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains all changes related to assertion model according to the constraint assertion model.
Using a script, we apply all assertion rules provided by the NUnit.Analyzers package. In addition, some manual interventions are done when applicable.
Plan of action