From 4343fd625e82d5d77c17806e533ca35a8d8aaa9a Mon Sep 17 00:00:00 2001 From: Enji Eid Date: Thu, 11 Jul 2024 12:35:41 +0200 Subject: [PATCH] Update mstest0025.md --- docs/core/testing/mstest-analyzers/mstest0025.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/core/testing/mstest-analyzers/mstest0025.md b/docs/core/testing/mstest-analyzers/mstest0025.md index 7b72ae6cc2d69..626f3ff63678e 100644 --- a/docs/core/testing/mstest-analyzers/mstest0025.md +++ b/docs/core/testing/mstest-analyzers/mstest0025.md @@ -39,7 +39,7 @@ Overall, using `Assert.Fail` promotes clarity, documentation, and maintainabilit ## How to fix violations -Ensure that calls to `Assert.IsTrue`, `Assert.IsFalse`, `Assert.AreEqual`, `Assert.AreNotEqual` or `Assert.IsNotNull` are not producing always-failing conditions. +Ensure that calls to `Assert.IsTrue`, `Assert.IsFalse`, `Assert.AreEqual`, `Assert.AreNotEqual`, `Assert.IsNull` or `Assert.IsNotNull` are not producing always-failing conditions. ## When to suppress warnings