MSTEST0053: Avoid using Assert methods with format parameters

[NOTE] This analyzer is no longer relevant for MSTest 4 as the assertion APIs with format parameters were removed.

Cause

An assertion method call uses the message and parameters arguments for string formatting instead of using string interpolation.

Rule description

Using the assertion overloads that accept message and parameters are no longer recommended. These overloads are removed in MSTest v4. It's advised to use string interpolation instead.

How to fix violations

Replace calls that use message format parameters with string interpolation.

For example, change this:

[TestMethod]
public void TestMethod()
{
    int expected = 5;
    int actual = GetValue();
    Assert.AreEqual(expected, actual, "Expected {0} but got {1}", expected, actual);
}

To this:

[TestMethod]
public void TestMethod()
{
    int expected = 5;
    int actual = GetValue();
    Assert.AreEqual(expected, actual, $"Expected {expected} but got {actual}");
}

When to suppress warnings

Don't suppress warnings from this rule. These overloads are removed in MSTest v4 and are not recommended.