Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support for NUnit 4 legacy asserts #606

Closed
OsirisTerje opened this issue Oct 5, 2023 · 2 comments · Fixed by #612
Closed

Support for NUnit 4 legacy asserts #606

OsirisTerje opened this issue Oct 5, 2023 · 2 comments · Fixed by #612
Assignees
@manfred-brands
Milestone
Release 3.10 / 2.10

Comments

@OsirisTerje
Copy link
Member

OsirisTerje commented Oct 5, 2023 •
edited
Loading

In NUnit 4 the classic Assert statements will be changed to ClassicAssert, and will be in the namespace NUnit.Framework.Legacy.

The rules that allow converting the classic asserts to the constraint model should include the ClassicAssert class.

Examples of using the classic asserts in NUnit 4 can be found here: https://github.com/nunit/nunit-csharp-samples
@OsirisTerje
Copy link
Member Author

@manfred-brands @mikkelbu We should get this one out before NUnit 4 non-beta is released :-)

@manfred-brands manfred-brands self-assigned this Oct 15, 2023
@manfred-brands
Copy link
Member

Yes, I know. We need to make a group of all items that need addressing before release 4.0.
I will create a new parent issue.

This was referenced Oct 15, 2023
Closed
Merged
@mikkelbu mikkelbu added this to the Release 3.10 / 2.10 milestone Oct 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@manfred-brands manfred-brands

Labels
None yet
Projects
None yet
Milestone
Release 3.10 / 2.10
Development

Successfully merging a pull request may close this issue.

Add support for NUnit version 4. manfred-brands/nunit.analyzers
3 participants
@OsirisTerje @mikkelbu @manfred-brands