Add support for NUnit version 4.

Detect ClassicAssert

Convert Classic format + params into InterpolatedString

documentation/NUnit1015.md

@@ -28,7 +28,7 @@ public class MyTestClass
     [TestCaseSource(typeof(DivideCases))]
     public void DivideTest(int n, int d, int q)
     {
-        Assert.AreEqual(q, n / d);
+        ClassicAssert.AreEqual(q, n / d);
     }
 }
 
@@ -59,7 +59,7 @@ public class MyTestClass
     [TestCaseSource(typeof(DivideCases))]
     public void DivideTest(int n, int d, int q)
     {
-        Assert.AreEqual(q, n / d);
+        ClassicAssert.AreEqual(q, n / d);
     }
 }
 

documentation/NUnit1016.md

@@ -28,7 +28,7 @@ public class MyTestClass
     [TestCaseSource(typeof(DivideCases))]
     public void DivideTest(int n, int d, int q)
     {
-        Assert.AreEqual(q, n / d);
+        ClassicAssert.AreEqual(q, n / d);
     }
 }
 
@@ -61,7 +61,7 @@ public class MyTestClass
     [TestCaseSource(typeof(DivideCases))]
     public void DivideTest(int n, int d, int q)
     {
-        Assert.AreEqual(q, n / d);
+        ClassicAssert.AreEqual(q, n / d);
     }
 }
 

documentation/NUnit1017.md

@@ -28,7 +28,7 @@ public class MyTestClass
     [TestCaseSource(nameof(DivideCases))]
     public void DivideTest(int n, int d, int q)
     {
-        Assert.AreEqual(q, n / d);
+        ClassicAssert.AreEqual(q, n / d);
     }
 
     object[] DivideCases =
@@ -56,7 +56,7 @@ public class MyTestClass
     [TestCaseSource(nameof(DivideCases))]
     public void DivideTest(int n, int d, int q)
     {
-        Assert.AreEqual(q, n / d);
+        ClassicAssert.AreEqual(q, n / d);
     }
 
     static object[] DivideCases =

documentation/NUnit1020.md

@@ -28,7 +28,7 @@ public class MyTestClass
     [TestCaseSource(nameof(DivideCases), new object[] { "Testing" })]
     public void DivideTest(int n, int d, int q)
     {
-        Assert.AreEqual(q, n / d);
+        ClassicAssert.AreEqual(q, n / d);
     }
 
     static object[] DivideCases =
@@ -54,7 +54,7 @@ public class MyTestClass
     [TestCaseSource(nameof(DivideCases), new object[] { "Testing" })]
     public void DivideTest(int n, int d, int q)
     {
-        Assert.AreEqual(q, n / d);
+        ClassicAssert.AreEqual(q, n / d);
     }
 
     static object[] DivideCases(string input)

documentation/NUnit1022.md

@@ -28,7 +28,7 @@ public class MyTestClass
     [Test]
     public void DivideTest([ValueSource(nameof(Numbers))] int n)
     {
-        Assert.AreEqual(n, Is.GreaterThanOrEqualTo(0));
+        ClassicAssert.AreEqual(n, Is.GreaterThanOrEqualTo(0));
     }
 
     object[] Numbers => new int[] { 1, 2, 3 };
@@ -51,7 +51,7 @@ public class MyTestClass
     [Test]
     public void DivideTest([ValueSource(nameof(Numbers))] int n)
     {
-        Assert.AreEqual(n, Is.GreaterThanOrEqualTo(0));
+        ClassicAssert.AreEqual(n, Is.GreaterThanOrEqualTo(0));
     }
 
     static object[] Numbers => new int[] { 1, 2, 3 };

documentation/NUnit2001.md

@@ -1,6 +1,6 @@
 # NUnit2001
 
-## Consider using Assert.That(expr, Is.False) instead of Assert.False(expr)
+## Consider using Assert.That(expr, Is.False) instead of ClassicAssert.False(expr)
 
 | Topic    | Value
 | :--      | :--
@@ -12,24 +12,24 @@
 
 ## Description
 
-Consider using the constraint model, `Assert.That(expr, Is.False)`, instead of the classic model, `Assert.False(expr)`.
+Consider using the constraint model, `Assert.That(expr, Is.False)`, instead of the classic model, `ClassicAssert.False(expr)`.
 
 ## Motivation
 
 The classic Assert model contains less flexibility than the constraint model,
-so this analyzer marks usages of `Assert.False` from the classic Assert model.
+so this analyzer marks usages of `ClassicAssert.False` from the classic Assert model.
 
 ```csharp
 [Test]
 public void Test()
 {
-    Assert.False(expression);
+    ClassicAssert.False(expression);
 }
 ```
 
 ## How to fix violations
 
-The analyzer comes with a code fix that will replace `Assert.False(expression)` with
+The analyzer comes with a code fix that will replace `ClassicAssert.False(expression)` with
 `Assert.That(expression, Is.False)`. So the code block above will be changed into.
 
 ```csharp
@@ -50,7 +50,7 @@ Configure the severity per project, for more info see [MSDN](https://learn.micro
 ### Via .editorconfig file
 
 ```ini
-# NUnit2001: Consider using Assert.That(expr, Is.False) instead of Assert.False(expr)
+# NUnit2001: Consider using Assert.That(expr, Is.False) instead of ClassicAssert.False(expr)
 dotnet_diagnostic.NUnit2001.severity = chosenSeverity
 ```
 
@@ -59,22 +59,22 @@ where `chosenSeverity` can be one of `none`, `silent`, `suggestion`, `warning`,
 ### Via #pragma directive
 
 ```csharp
-#pragma warning disable NUnit2001 // Consider using Assert.That(expr, Is.False) instead of Assert.False(expr)
+#pragma warning disable NUnit2001 // Consider using Assert.That(expr, Is.False) instead of ClassicAssert.False(expr)
 Code violating the rule here
-#pragma warning restore NUnit2001 // Consider using Assert.That(expr, Is.False) instead of Assert.False(expr)
+#pragma warning restore NUnit2001 // Consider using Assert.That(expr, Is.False) instead of ClassicAssert.False(expr)
 ```
 
 Or put this at the top of the file to disable all instances.
 
 ```csharp
-#pragma warning disable NUnit2001 // Consider using Assert.That(expr, Is.False) instead of Assert.False(expr)
+#pragma warning disable NUnit2001 // Consider using Assert.That(expr, Is.False) instead of ClassicAssert.False(expr)
 ```
 
 ### Via attribute `[SuppressMessage]`
 
 ```csharp
 [System.Diagnostics.CodeAnalysis.SuppressMessage("Assertion",
-    "NUnit2001:Consider using Assert.That(expr, Is.False) instead of Assert.False(expr)",
+    "NUnit2001:Consider using Assert.That(expr, Is.False) instead of ClassicAssert.False(expr)",
     Justification = "Reason...")]
 ```
 <!-- end generated config severity -->

documentation/NUnit2002.md

@@ -1,6 +1,6 @@
 # NUnit2002
 
-## Consider using Assert.That(expr, Is.False) instead of Assert.IsFalse(expr)
+## Consider using Assert.That(expr, Is.False) instead of ClassicAssert.IsFalse(expr)
 
 | Topic    | Value
 | :--      | :--
@@ -12,24 +12,24 @@
 
 ## Description
 
-Consider using the constraint model, `Assert.That(expr, Is.False)`, instead of the classic model, `Assert.IsFalse(expr)`.
+Consider using the constraint model, `Assert.That(expr, Is.False)`, instead of the classic model, `ClassicAssert.IsFalse(expr)`.
 
 ## Motivation
 
 The classic Assert model contains less flexibility than the constraint model,
-so this analyzer marks usages of `Assert.IsFalse` from the classic Assert model.
+so this analyzer marks usages of `ClassicAssert.IsFalse` from the classic Assert model.
 
 ```csharp
 [Test]
 public void Test()
 {
-    Assert.IsFalse(expression);
+    ClassicAssert.IsFalse(expression);
 }
 ```
 
 ## How to fix violations
 
-The analyzer comes with a code fix that will replace `Assert.IsFalse(expression)` with
+The analyzer comes with a code fix that will replace `ClassicAssert.IsFalse(expression)` with
 `Assert.That(expression, Is.False)`. So the code block above will be changed into.
 
 ```csharp
@@ -50,7 +50,7 @@ Configure the severity per project, for more info see [MSDN](https://learn.micro
 ### Via .editorconfig file
 
 ```ini
-# NUnit2002: Consider using Assert.That(expr, Is.False) instead of Assert.IsFalse(expr)
+# NUnit2002: Consider using Assert.That(expr, Is.False) instead of ClassicAssert.IsFalse(expr)
 dotnet_diagnostic.NUnit2002.severity = chosenSeverity
 ```
 
@@ -59,22 +59,22 @@ where `chosenSeverity` can be one of `none`, `silent`, `suggestion`, `warning`,
 ### Via #pragma directive
 
 ```csharp
-#pragma warning disable NUnit2002 // Consider using Assert.That(expr, Is.False) instead of Assert.IsFalse(expr)
+#pragma warning disable NUnit2002 // Consider using Assert.That(expr, Is.False) instead of ClassicAssert.IsFalse(expr)
 Code violating the rule here
-#pragma warning restore NUnit2002 // Consider using Assert.That(expr, Is.False) instead of Assert.IsFalse(expr)
+#pragma warning restore NUnit2002 // Consider using Assert.That(expr, Is.False) instead of ClassicAssert.IsFalse(expr)
 ```
 
 Or put this at the top of the file to disable all instances.
 
 ```csharp
-#pragma warning disable NUnit2002 // Consider using Assert.That(expr, Is.False) instead of Assert.IsFalse(expr)
+#pragma warning disable NUnit2002 // Consider using Assert.That(expr, Is.False) instead of ClassicAssert.IsFalse(expr)
 ```
 
 ### Via attribute `[SuppressMessage]`
 
 ```csharp
 [System.Diagnostics.CodeAnalysis.SuppressMessage("Assertion",
-    "NUnit2002:Consider using Assert.That(expr, Is.False) instead of Assert.IsFalse(expr)",
+    "NUnit2002:Consider using Assert.That(expr, Is.False) instead of ClassicAssert.IsFalse(expr)",
     Justification = "Reason...")]
 ```
 <!-- end generated config severity -->

documentation/NUnit2003.md

@@ -1,6 +1,6 @@
 # NUnit2003
 
-## Consider using Assert.That(expr, Is.True) instead of Assert.IsTrue(expr)
+## Consider using Assert.That(expr, Is.True) instead of ClassicAssert.IsTrue(expr)
 
 | Topic    | Value
 | :--      | :--
@@ -12,24 +12,24 @@
 
 ## Description
 
-Consider using the constraint model, `Assert.That(expr, Is.True)`, instead of the classic model, `Assert.IsTrue(expr)`.
+Consider using the constraint model, `Assert.That(expr, Is.True)`, instead of the classic model, `ClassicAssert.IsTrue(expr)`.
 
 ## Motivation
 
 The classic Assert model contains less flexibility than the constraint model,
-so this analyzer marks usages of `Assert.IsTrue` from the classic Assert model.
+so this analyzer marks usages of `ClassicAssert.IsTrue` from the classic Assert model.
 
 ```csharp
 [Test]
 public void Test()
 {
-    Assert.IsTrue(expression);
+    ClassicAssert.IsTrue(expression);
 }
 ```
 
 ## How to fix violations
 
-The analyzer comes with a code fix that will replace `Assert.IsTrue(expression)` with
+The analyzer comes with a code fix that will replace `ClassicAssert.IsTrue(expression)` with
 `Assert.That(expression, Is.True)`. So the code block above will be changed into.
 
 ```csharp
@@ -50,7 +50,7 @@ Configure the severity per project, for more info see [MSDN](https://learn.micro
 ### Via .editorconfig file
 
 ```ini
-# NUnit2003: Consider using Assert.That(expr, Is.True) instead of Assert.IsTrue(expr)
+# NUnit2003: Consider using Assert.That(expr, Is.True) instead of ClassicAssert.IsTrue(expr)
 dotnet_diagnostic.NUnit2003.severity = chosenSeverity
 ```
 
@@ -59,22 +59,22 @@ where `chosenSeverity` can be one of `none`, `silent`, `suggestion`, `warning`,
 ### Via #pragma directive
 
 ```csharp
-#pragma warning disable NUnit2003 // Consider using Assert.That(expr, Is.True) instead of Assert.IsTrue(expr)
+#pragma warning disable NUnit2003 // Consider using Assert.That(expr, Is.True) instead of ClassicAssert.IsTrue(expr)
 Code violating the rule here
-#pragma warning restore NUnit2003 // Consider using Assert.That(expr, Is.True) instead of Assert.IsTrue(expr)
+#pragma warning restore NUnit2003 // Consider using Assert.That(expr, Is.True) instead of ClassicAssert.IsTrue(expr)
 ```
 
 Or put this at the top of the file to disable all instances.
 
 ```csharp
-#pragma warning disable NUnit2003 // Consider using Assert.That(expr, Is.True) instead of Assert.IsTrue(expr)
+#pragma warning disable NUnit2003 // Consider using Assert.That(expr, Is.True) instead of ClassicAssert.IsTrue(expr)
 ```
 
 ### Via attribute `[SuppressMessage]`
 
 ```csharp
 [System.Diagnostics.CodeAnalysis.SuppressMessage("Assertion",
-    "NUnit2003:Consider using Assert.That(expr, Is.True) instead of Assert.IsTrue(expr)",
+    "NUnit2003:Consider using Assert.That(expr, Is.True) instead of ClassicAssert.IsTrue(expr)",
     Justification = "Reason...")]
 ```
 <!-- end generated config severity -->

documentation/NUnit2004.md

@@ -1,6 +1,6 @@
 # NUnit2004
 
-## Consider using Assert.That(expr, Is.True) instead of Assert.True(expr)
+## Consider using Assert.That(expr, Is.True) instead of ClassicAssert.True(expr)
 
 | Topic    | Value
 | :--      | :--
@@ -12,24 +12,24 @@
 
 ## Description
 
-Consider using the constraint model, `Assert.That(expr, Is.True)`, instead of the classic model, `Assert.True(expr)`.
+Consider using the constraint model, `Assert.That(expr, Is.True)`, instead of the classic model, `ClassicAssert.True(expr)`.
 
 ## Motivation
 
 The classic Assert model contains less flexibility than the constraint model,
-so this analyzer marks usages of `Assert.True` from the classic Assert model.
+so this analyzer marks usages of `ClassicAssert.True` from the classic Assert model.
 
 ```csharp
 [Test]
 public void Test()
 {
-    Assert.True(expression);
+    ClassicAssert.True(expression);
 }
 ```
 
 ## How to fix violations
 
-The analyzer comes with a code fix that will replace `Assert.True(expression)` with
+The analyzer comes with a code fix that will replace `ClassicAssert.True(expression)` with
 `Assert.That(expression, Is.True)`. So the code block above will be changed into.
 
 ```csharp
@@ -50,7 +50,7 @@ Configure the severity per project, for more info see [MSDN](https://learn.micro
 ### Via .editorconfig file
 
 ```ini
-# NUnit2004: Consider using Assert.That(expr, Is.True) instead of Assert.True(expr)
+# NUnit2004: Consider using Assert.That(expr, Is.True) instead of ClassicAssert.True(expr)
 dotnet_diagnostic.NUnit2004.severity = chosenSeverity
 ```
 
@@ -59,22 +59,22 @@ where `chosenSeverity` can be one of `none`, `silent`, `suggestion`, `warning`,
 ### Via #pragma directive
 
 ```csharp
-#pragma warning disable NUnit2004 // Consider using Assert.That(expr, Is.True) instead of Assert.True(expr)
+#pragma warning disable NUnit2004 // Consider using Assert.That(expr, Is.True) instead of ClassicAssert.True(expr)
 Code violating the rule here
-#pragma warning restore NUnit2004 // Consider using Assert.That(expr, Is.True) instead of Assert.True(expr)
+#pragma warning restore NUnit2004 // Consider using Assert.That(expr, Is.True) instead of ClassicAssert.True(expr)
 ```
 
 Or put this at the top of the file to disable all instances.
 
 ```csharp
-#pragma warning disable NUnit2004 // Consider using Assert.That(expr, Is.True) instead of Assert.True(expr)
+#pragma warning disable NUnit2004 // Consider using Assert.That(expr, Is.True) instead of ClassicAssert.True(expr)
 ```
 
 ### Via attribute `[SuppressMessage]`
 
 ```csharp
 [System.Diagnostics.CodeAnalysis.SuppressMessage("Assertion",
-    "NUnit2004:Consider using Assert.That(expr, Is.True) instead of Assert.True(expr)",
+    "NUnit2004:Consider using Assert.That(expr, Is.True) instead of ClassicAssert.True(expr)",
     Justification = "Reason...")]
 ```
 <!-- end generated config severity -->