MSTEST0039: Use newer 'Assert.Throws' methods
| Property | Value |
|---|---|
| Rule ID | MSTEST0039 |
| Title | Use newer 'Assert.Throws' methods |
| Category | Usage |
| Fix is breaking or non-breaking | Non-breaking |
| Enabled by default | Yes |
| Default severity | Info |
| Introduced in version | 3.8.0 |
| Is there a code fix | Yes |
Cause
The use of <xref:Microsoft.VisualStudio.TestTools.UnitTesting.Assert.ThrowsException*?displayProperty=nameWithType> or <xref:Microsoft.VisualStudio.TestTools.UnitTesting.Assert.ThrowsExceptionAsync*?displayProperty=nameWithType>, which are no longer recommended.
Rule description
<xref:Microsoft.VisualStudio.TestTools.UnitTesting.Assert.ThrowsException*?displayProperty=nameWithType> and <xref:Microsoft.VisualStudio.TestTools.UnitTesting.Assert.ThrowsExceptionAsync*?displayProperty=nameWithType> are not recommended and might be deprecated in the future.
How to fix violations
Use Assert.ThrowsExactly or Assert.ThrowsExactlyAsync instead of Assert.ThrowsException or Assert.ThrowsExceptionAsync.
When to suppress warnings
Do not suppress a warning from this rule. It's strongly recommended to move from the old APIs to the new ones.
