How to Hide the StackTrace of the Custom Extension Method on Assert.That From the Text Output Window?

I’ve created my own extension methods on the non static Assert class usable via the Assert.That singleton in the expected manner I’m assuming is correct:

[DebuggerHidden]
public static void ExistsLineContaining(this Assert assert, string[] lines, string value, string message = null)
{
    Assert.IsTrue(lines.Count(l => l.Contains(value)) >= 1, message);
}

but when my test fails, the stack trace shows the ExistsLineContaining extension method as the first value in the trace:

This is really not ideal. I can work around it slightly by putting it in a separate assembly, and turning off debug information from being generated, but this is again really not ideal, and it doesn’t solve the problem of the line from showing up in the test output (but at least it’s not clickable): Is there any supported method to give these extension methods more of a “First Class” feel to them by preventing them from showing in the stack trace of the test output?

[karanjitsingh]

@daryllabar, Good question! It seems we exclude certain types from the stack trace here

Which made me realize that we have a workaround for you, all you have to do is keep your extension method under the namespace Microsoft.VisualStudio.TestPlatform.MSTest.TestAdapter

Apologies for the confusion earlier!

[acesiddhu]

Closing the issue. Please make changes as @karanjitsingh suggested