Suggestions to use fluent assertions instead of MSTest Asserts do not work if "using Microsoft.VisualStudio.TestTools.UnitTesting;" is located inside of the namespace.

Description

Newly added functionality enabling easy move from MSTest Asserts to fluent assertions does not work if “using Microsoft.VisualStudio.TestTools.UnitTesting;” is located inside of the namespace.

Complete minimal example reproducing the issue

This will get a suggestion:

using Microsoft.VisualStudio.TestTools.UnitTesting;

namespace TestProject1
{
    [TestClass]
    public class UnitTest1
    {
        [TestMethod]
        public void TestMethod1()
        {
            Assert.AreEqual(1, 1);
        }
    }
}

But this will not:

namespace TestProject1
{
    using Microsoft.VisualStudio.TestTools.UnitTesting;

    [TestClass]
    public class UnitTest1
    {
        [TestMethod]
        public void TestMethod1()
        {
            Assert.AreEqual(1, 1);
        }
    }
}

Expected behavior:

Suggestion to use fluent assertions instead of Assert is shown when “using Microsoft.VisualStudio.TestTools.UnitTesting;” is located inside of the namespace.

Actual behavior:

Suggestion to use fluent assertions instead of Assert is not shown when “using Microsoft.VisualStudio.TestTools.UnitTesting;” is located inside of the namespace.

Versions

• Which version of Fluent Assertions Analyzers are you using? FluentAssertions.Analyzers 0.16.0
• Which .NET runtime and version are you targeting? .NET Core 3.1.

[Meir017]

@robertMSFTE should be working now with version 0.17.2

[Meir017]

@robertMSFTE just published version 0.17.1 with fixed package