Run omnisharp test commands from vscode #35
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi @rawman! Thanks for the PR! The C# team (e.g. https://github.com/dotnet/roslyn) now owns this extension as the official C# experience in Visual Studio Code. We're currently working on adding support to make the extension target .NET Core and have some pretty substantial experience changes coming soon. Please stay tuned. |
|
@rawman, unfortunately, we won't be able to take this PR, but we really appreciate you taking the time to submit. We will be investing in the testing experience for this extension in the coming months, so you'll definitely see improvements there. |
This was referenced Dec 14, 2020
dibarbet
added a commit
to dibarbet/vscode-csharp
that referenced
this pull request
Jun 8, 2023
Add scheduled merge from omnisharp-vscode for master and feature/lsp-engine
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @jrieken
First I would like to thank you for a great extension, I love it!
This PR introduces running omnisharp test commands inside vscode output channel. There are three commands:
How does it work:
Test output is displayed in standard output channel like any other task. Additionally test execution summary i.e.
Total: 2, Errors: 0, Failed: 1, Skipped: 0, Time: 0.110sis displayed in status bar. If one of tests fails, output channel is opened at the end of execution, otherwise not so you are not disturbed when tests went smoothly. Currently XUnit and NUnit output format is supported. Those formats right now are hardcoded which I don't like too much, but I don't see better way to understand test output.Let me know what do you think. I'm starting to play with TypeScript so I hope I didn't make any horrible things ;)