Mention Assert.Throws and Assert.ThrowsExactly in docs (#44160)

Author: Youssef1313

docs/core/testing/mstest-analyzers/design-rules.md

@@ -13,7 +13,7 @@ Design rules will help you create and maintain test suites that adhere to proper
 Identifier | Name | Description
 -----------|------|------------
 [MSTEST0004](mstest0004.md) | PublicTypeShouldBeTestClassAnalyzer | It's considered a good practice to have only test classes marked public in a test project.
-[MSTEST0006](mstest0006.md) | AvoidExpectedExceptionAttributeAnalyzer | Prefer `Assert.ThrowsException` or `Assert.ThrowsExceptionAsync` over `[ExpectedException]` as it ensures that only the expected call throws the expected exception. The assert APIs also provide more flexibility and allow you to assert extra properties of the exception.
+[MSTEST0006](mstest0006.md) | AvoidExpectedExceptionAttributeAnalyzer | Prefer `Assert.ThrowsExactly` or `Assert.ThrowsExactlyAsync` over `[ExpectedException]` as it ensures that only the expected call throws the expected exception. The assert APIs also provide more flexibility and allow you to assert extra properties of the exception.
 [MSTEST0015](mstest0015.md) | TestMethodShouldNotBeIgnored | Test methods should not be ignored (marked with `[Ignore]`).
 [MSTEST0016](mstest0016.md) | TestClassShouldHaveTestMethod | Test class should have at least one test method or be 'static' with method(s) marked by `[AssemblyInitialization]` and/or `[AssemblyCleanup]`.
 [MSTEST0019](mstest0019.md) | PreferTestInitializeOverConstructorAnalyzer | Prefer TestInitialize methods over constructors

docs/core/testing/mstest-analyzers/mstest0006.md

@@ -33,7 +33,7 @@ A method is marked with the `[ExpectedException]` attribute.
 
 ## Rule description
 
-Prefer `Assert.ThrowsException` or `Assert.ThrowsExceptionAsync` over the `[ExpectedException]` attribute as it ensures that only the expected line of code throws the expected exception, instead of acting on the whole body of the test. The assert APIs also provide more flexibility and allow you to assert extra properties of the exception.
+Prefer `Assert.ThrowsException` or `Assert.ThrowsExceptionAsync` (or `Assert.ThrowsExactly`/`Assert.Throws` or `Assert.ThrowsExactlyAsync`/`Assert.ThrowsAsync` if using MSTest 3.8 and later) over the `[ExpectedException]` attribute as it ensures that only the expected line of code throws the expected exception, instead of acting on the whole body of the test. The assert APIs also provide more flexibility and allow you to assert extra properties of the exception.
 
 ```csharp
 [TestClass]
@@ -59,7 +59,7 @@ public class TestClass
 
 ## How to fix violations
 
-Replace the usage of the `[ExpectedException]` attribute by a call to `Assert.ThrowsException` or `Assert.ThrowsExceptionAsync`.
+Replace the usage of the `[ExpectedException]` attribute by a call to `Assert.ThrowsException` or `Assert.ThrowsExceptionAsync` (or `Assert.ThrowsExactly`/`Assert.Throws` or `Assert.ThrowsExactlyAsync`/`Assert.ThrowsAsync` if using MSTest 3.8 and later).
 
 ```csharp
 [TestClass]
@@ -77,7 +77,7 @@ public class TestClass
         person.SetAge(-1);
 
         // Act
-        Assert.ThrowsException(() => person.GrowOlder());
+        Assert.ThrowsExactly(() => person.GrowOlder());
     }
 }
 ```

docs/core/testing/unit-testing-mstest-writing-tests-attributes.md

@@ -390,7 +390,7 @@ public class UnitTest1
 The MSTest framework introduced <xref:Microsoft.VisualStudio.TestTools.UnitTesting.ExpectedExceptionAttribute> for marking a test method to expect an exception of a specific type. The test will pass if the expected exception is thrown and the exception message matches the expected message.
 
 > [!WARNING]
-> This attribute exists for backward compatibility and is not recommended for new tests. Instead, use the `Assert.ThrowsException` method.
+> This attribute exists for backward compatibility and is not recommended for new tests. Instead, use the `Assert.ThrowsException` (or `Assert.ThrowsExactly` if using MSTest 3.8 and later) method.
 
 ## Metadata attributes
 

docs/core/tutorials/testing-library-with-visual-studio-code.md

@@ -67,7 +67,7 @@ The most common tests call members of the <xref:Microsoft.VisualStudio.TestTools
 | `Assert.IsFalse`   | Verifies that a condition is `false`. The assert fails if the condition is `true`. |
 | `Assert.IsNotNull` | Verifies that an object isn't `null`. The assert fails if the object is `null`. |
 
-You can also use the <xref:Microsoft.VisualStudio.TestTools.UnitTesting.Assert.ThrowsException%2A?displayProperty=nameWithType> method in a test method to indicate the type of exception it's expected to throw. The test fails if the specified exception isn't thrown.
+You can also use the <xref:Microsoft.VisualStudio.TestTools.UnitTesting.Assert.ThrowsException%2A?displayProperty=nameWithType> (or `Assert.Throws` and `Assert.ThrowsExactly` if using MSTest 3.8 and later) method in a test method to indicate the type of exception it's expected to throw. The test fails if the specified exception isn't thrown.
 
 In testing the `StringLibrary.StartsWithUpper` method, you want to provide a number of strings that begin with an uppercase character. You expect the method to return `true` in these cases, so you can call the <xref:Microsoft.VisualStudio.TestTools.UnitTesting.Assert.IsTrue%2A?displayProperty=nameWithType> method. Similarly, you want to provide a number of strings that begin with something other than an uppercase character. You expect the method to return `false` in these cases, so you can call the <xref:Microsoft.VisualStudio.TestTools.UnitTesting.Assert.IsFalse%2A?displayProperty=nameWithType> method.
 

docs/core/tutorials/testing-library-with-visual-studio.md

@@ -95,7 +95,7 @@ The most common tests call members of the <xref:Microsoft.VisualStudio.TestTools
 | `Assert.IsFalse`   | Verifies that a condition is `false`. The assert fails if the condition is `true`. |
 | `Assert.IsNotNull` | Verifies that an object isn't `null`. The assert fails if the object is `null`. |
 
-You can also use the <xref:Microsoft.VisualStudio.TestTools.UnitTesting.Assert.ThrowsException%2A?displayProperty=nameWithType> method in a test method to indicate the type of exception it's expected to throw. The test fails if the specified exception isn't thrown.
+You can also use the <xref:Microsoft.VisualStudio.TestTools.UnitTesting.Assert.ThrowsException%2A?displayProperty=nameWithType> (or `Assert.Throws` and `Assert.ThrowsExactly` if using MSTest 3.8 and later) method in a test method to indicate the type of exception it's expected to throw. The test fails if the specified exception isn't thrown.
 
 In testing the `StringLibrary.StartsWithUpper` method, you want to provide a number of strings that begin with an uppercase character. You expect the method to return `true` in these cases, so you can call the <xref:Microsoft.VisualStudio.TestTools.UnitTesting.Assert.IsTrue%2A?displayProperty=nameWithType> method. Similarly, you want to provide a number of strings that begin with something other than an uppercase character. You expect the method to return `false` in these cases, so you can call the <xref:Microsoft.VisualStudio.TestTools.UnitTesting.Assert.IsFalse%2A?displayProperty=nameWithType> method.