CharliePoole

Have you tried using `{C}.{m}{a}`?

According to our docs, `{m}`, `{M}`, `{c}` and `{C}` are supposed to include the fixture arguments. However, this seems like a documentation error to me, since we have always specified...

@jnm2 Keep in mind that the name and fullname of a __test__ are not the same thing as the name and fullname of a test method! IMO, the first thing...

@gustafj There's no way to do that. You can only modify one test at a time. If you were allowed to modify it in the constructor, it would already be...

@jnm2 You seemed to be expecting {M} and {C} to include args, which is outside the definition method or type names, while it's part of the definition of NUnit test...

Ah! You're right WRT the Test FullName. The Name is still only `Namespace.FixtureName.MethodName`. So that code was needed at some point because of how the tree of tests is processed....

@jnm2 I don't know what the adapter is doing, I'm afraid. I've been off that team for about a year.

@gustafj As far as I know that's true, but I haven't worked on the adapter for about a year. Note that in the context of this __framework__ issue, the only...

@jnm2 It seems like that approach (reporting `fullname`) would solve the problem for the adapter without any changes at all to TSL. So do any runners that do __not__ use...

I like the idea of giving the adapter some kind of option as to how it reports test names to VS. But the details would have to be worked out...