docs/articles/nunit-analyzers/NUnit2018.md
| Topic | Value |
|---|---|
| Id | NUnit2018 |
| Severity | Info |
| Enabled | True |
| Category | Assertion |
| Code | ClassicModelAssertUsageAnalyzer |
Consider using the constraint model, Assert.That(expr, Is.Not.Null), instead of the classic model,
ClassicAssert.NotNull(expr).
The classic Assert model contains less flexibility than the constraint model,
so this analyzer marks usages of ClassicAssert.NotNull from the classic Assert model.
[Test]
public void Test()
{
object obj = null;
ClassicAssert.NotNull(obj);
}
The analyzer comes with a code fix that will replace ClassicAssert.NotNull(expression) with
Assert.That(expression, Is.Not.Null). So the code block above will be changed into.
[Test]
public void Test()
{
object obj = null;
Assert.That(obj, Is.Not.Null);
}
Configure the severity per project, for more info see MSDN.
# NUnit2018: Consider using Assert.That(expr, Is.Not.Null) instead of ClassicAssert.NotNull(expr)
dotnet_diagnostic.NUnit2018.severity = chosenSeverity
where chosenSeverity can be one of none, silent, suggestion, warning, or error.
#pragma warning disable NUnit2018 // Consider using Assert.That(expr, Is.Not.Null) instead of ClassicAssert.NotNull(expr)
Code violating the rule here
#pragma warning restore NUnit2018 // Consider using Assert.That(expr, Is.Not.Null) instead of ClassicAssert.NotNull(expr)
Or put this at the top of the file to disable all instances.
#pragma warning disable NUnit2018 // Consider using Assert.That(expr, Is.Not.Null) instead of ClassicAssert.NotNull(expr)
[SuppressMessage][System.Diagnostics.CodeAnalysis.SuppressMessage("Assertion",
"NUnit2018:Consider using Assert.That(expr, Is.Not.Null) instead of ClassicAssert.NotNull(expr)",
Justification = "Reason...")]