Unclear how to run tests

bamurtaugh commented 1 year ago

Describe the Issue

I'm not sure if this was a bug or if it's a feature request, so please feel free to adjust/label as appropriate 😄.

Following the testing guidance in docs and the Testing UI in VS Code, I wasn't sure how to run tests. I eventually ran a test successfully, but I felt a bit like I was guessing.

Steps To Reproduce

Open Test Explorer in VS Code, see there are no tests configured
Follow the doc steps and configure MSTest
Based on the info and image in docs, I thought I'd see something in the Test Explorer at this point
Not sure how I should run my test, so try command Test: Run all Tests
Test runs successfully, and now I see content in my Test Explorer:

Expected Behavior

To see the content in the Test Explorer after adding a test so that I could've run it from there to begin with.

Environment Information

I'm using a .NET dev container with the latest VS Code Insiders on Windows 11 Insiders.

Version: 1.80.0-insider (user setup) Commit: 79c4092768e41b16fd823e80c874dbfafdc08f55 Date: 2023-06-13T05:21:23.732Z Electron: 22.5.5 Chromium: 108.0.5359.215 Node.js: 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0.25387

timheuer commented 1 year ago

@bamurtaugh I mistakenly assumed that Test Explorer UI as a part of the shell of VS Code was documented since the pattern of running tests is the same there for adapters. Is there a reason we don't elevate a single place for VS Code docs for this rather than defer the simple "how to run" aspects in each language section (which feels repetitive)?

bamurtaugh commented 1 year ago

Thanks @timheuer for the context!

Is there a reason we don't elevate a single place for VS Code docs for this rather than defer the simple "how to run" aspects in each language section (which feels repetitive)?

This is a great question that perhaps @gregvanl or @connor4312 have thoughts on? And @gregvanl if you think this should be moved / adjusted to more of an overall VS Code docs issue (rather than .NET specific), please let me know

AbhitejJohn commented 1 year ago

This could be related to Source based discovery support that would automatically discover and display tests in the Test Explorer. We haven't added that support in just yet

microsoft / vscode-dotnettools