Open pkrukp opened 6 years ago
Here is the fix that was done to the current adapter: https://github.com/nunit/nunit3-vs-adapter/pull/285
That pull request was merged in a year ago. Why is this still a problem? We are still setting the issue resolved by #285 when upgrading to 3.9 from 2.6.4 in visual studio 2017. "No source available"
@OsirisTerje Should we move this to the nunit3 adapter repo?
From my (test adapter user) perspective, if I had problem with test adapter v2, I would search issues in test adapter v2 github project, not v3.
If problem also occurs in test adapter v3 (I think I also tested v3 and I think this problem did not happen for me - I'm not 100% sure) I would prefer to have a separate issue created in the v3 github project.
If it's a problem in the v2 adapter, then it belongs here. If other people have a problem on v3, we may need a separate issue.
The reason I asked is that we're doing our best to move people to v3 and the v3 adapter to focus our efforts there rather than publish a new v2 adapter.
Understood. My comment was meant to reflect my disagreement with that policy.
Hi,
if inner (nested) class is marked with TestFixture, then there is no information about source code:
The source information is not present at least for parametrized tests, I have not checked normal tests. The lack of source information can be seen in VS Test Explorar, but also when using vstest programmatically through VsTestConsoleWrapper.
Attaching Nested.zip - solution with:
Reproduction steps: