Terje Sandstrom

Do you see the same if you use e.g. version 3.17.0 ?

@varnk I have just checked your repo with VS 2017, 15.9., and with Adapter 4.2.1 I am not able to run the tests at all, when doing one-by-one. Downgrading to...

@varnk Can you reproduce this on more than one machine? (The VS2017 dysfunction with 4.2.1, and if it works with 3.17 or not.) If you can, there must be some...

This is a known issue, part of the FQN issues.

@plainionist This issue seems now to be fixed in the latest version of Visual Studio 2019, 16.11.3.  See repro here: https://github.com/nunit/nunit3-vs-adapter.issues/tree/master/Issue711 Note that the '.' in the name causes...

Reopened. @plainionist Can you confirm the repro at https://github.com/nunit/nunit3-vs-adapter.issues/tree/master/Issue711 reproduces your issue? If not, can you update it so that it does?

The problem with spaces in names is that the test names are very close to FQN for classes and namespaces, and as they can't have spaces, the test names can't...

The adapter tries to deduct from where it is being called, there are properties being set to that effect. But you then have to bring that information all the way...

You should not pass the information to the tokenizer, but create a new (derived) class for it, so that you change the method there. That way the existing code is...

@AnastasiaDen16 And what is your test expression ?