VS "Show in Test Explorer" doesn't work for F#
See original GitHub issueRepro steps
- In an F# solution
- Go to some Xunit/Nunit test (place cursor on definition line or inside the test code)
- Issue “Show in Test Explorer” command (either via context menu, Feature Search, or
Ctrl + E, S
)
Expected behavior
- Test Explorer is shown
- The test case is selected
Actual behavior
- Test Explorer is shown
- Some top-level test group is selected
Known workarounds
Find the test manually
Related information
Doesn’t work on test function definition, module, namespace
Observed in these versions:
- 17.5 preview 3
- 17.6 preview 1
Issue Analytics
- State:
- Created 8 months ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Visual Studio Test Explorer doesn't show results
Visual Studio's Test Explorer was not showing the icons that indicate whether tests passed or failed. There were additional problems. I'd tried ...
Read more >Test Explorer not discoverying test methods
First, check if your target platform has the correct value. Second, Open the Output Pane, and choose "Tests" from "Show output from:" dropdown ......
Read more >Add Problems doesn't work for Expecto tests. #233
I have two test projects in my workspace, one made via 'dotnet new xunit -lang F#' and the other via 'dotnet new expecto'....
Read more >Run unit tests with Test Explorer - Visual Studio (Windows)
If Test Explorer is not visible, choose Test on the Visual Studio menu, choose Windows, and then choose Test Explorer (or press Ctrl...
Read more >The Eleventh Off-Campus Library Services Conference Proceedings
Click on existing file or webpage button. 7. ... that contained a “helper” program that opens Internet Explorer in order to run the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@vzarytovskii That’s the issue I was talking to you about when I joined and totally forgot to log.
I haven’t investigated the issue but my understanding is that this is linked to some incorrect position being either detected or reported (I would think this is some improvement we need to do on TP but not 100% sure). If @nohwnd hasn’t replied in the meantime, I will try to understand TP code logic and see if my assumption is right or not.
@nohwnd it happens even if there is no
<Empty Namespace>
anywhere in the test tree.