Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Specify target framework when discovering tests

See original GitHub issue

First of all, thanks for this awesome extension. Great work 👍

Would it be possible to somehow specify the target framework when doing test discovery?

Either group them in the explorer by target framework or simply make it a configuration value that can be passed to dotnet test -f netcoreapp2.0 -t -v=q. Right Now you can’t really Go to test since there are multiple matching symbols when you have a test project that is cross compiled.

Issue Analytics

State:
Created 5 years ago
Comments:10 (5 by maintainers)

Top GitHub Comments

1reaction

seesharpercommented, Sep 6, 2018

I tool a quick look at it and in the case I’ve described previously, the location of the methods are identical. Which means the we could take the method location into consideration when trying to come up with an unique symbol. If they are different, which should be rare, it makes sense to either abort or give the user the ability to choose.

0reactions

stefanforsbergcommented, Sep 26, 2018

Should be fixed with 0.5.4