-
-
Notifications
You must be signed in to change notification settings - Fork 453
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
Migrate to Nunit4 #2705
Migrate to Nunit4 #2705
Conversation
I'm glad that you didn't have to do that manually! |
I would try to land this soon. And we could work in some improvements later. |
@kblok the new NUnit analyzers pointed out methods that contained assertions, but weren't annotated with We could cherry-pick that commit to another PR with other changes necessary to have them pass on master as well. |
lib/PuppeteerSharp.Tests/BrowserContextTests/BrowserContextOverridePermissionsTests.cs
Outdated
Show resolved
Hide resolved
lib/PuppeteerSharp.Tests/ElementHandleTests/ContentFrameTests.cs
Outdated
Show resolved
Hide resolved
lib/PuppeteerSharp.Tests/EvaluationTests/PageEvaluateOnNewDocumentTests.cs
Outdated
Show resolved
Hide resolved
@jnyrup do you think we can land this? |
I don't have any pending changes. There's a failing tests with an NRE, I haven't looked into the cause of that, but I guess it's unrelated to this PR. |
The first commit migrates from from NUnit3 to NUnit4.
All the changes to the new
Assert.That
syntax (Called the constraint model) where done automatically by the added NUnit.Analyzers.Their list of analyzers.
In the second commit I went through the warnings from NUnit1028 which warns about public methods in test classes that are not marked with
[Test]
.I've blindly added
[Test]
to all those that had asserts in them.