Steven Weerdenburg

@OsirisTerje sorry, I had missed that you had pinged for thoughts here. I'm not at a computer for a few days, but will try to look soon. Definitely need to...

Oh, reading further I see that perhaps this is on the filtering side, as you mention.

I've been able to experiment a bit with the repro. It seemed as though commenting out the ignore didn't change anything, though the presence of another test did seem to...

I'm beginning to wonder if this is a line endings issue within the test name. I see `\r\n` here in `DefaultTestCaseBuilder.BuildFrom`  And `\n` here in the passed in filter...

To be honest, I hadn't thought of the `Assert.*` asserts as being movable into a separate package, only the `*Assert.*` ones like `StringAssert`, etc. Though I could see the argument...

This doesn't appear related to the in filter optimization as commenting it out doesn't seem to change anything.

I just realized that last example would break if the code that followed were: ```csharp var foo = Assert.ThrowsAsync(async () => {}); Exception result = await foo; ``` As the...

Just revisiting the conversation here to ensure consensus after the analyzer digression. If I understand the conversation above, it sounds like we're considering nudging users towards an `ClassicAssert.Throws(Func)` overload in...

I've been able to make a test over this which seems to reproduce the issue but I wouldn't say I'm "close". I'll push a branch in a few hours to...

@OsirisTerje I've found that the XML generated for the test method above doesn't roundtrip when calling `TNode.ToXML` and `TNode.FromXml` again. I suspect this to be the underlying issue here. We've...