Add nextest support to Run Test and Run Tests - #1155
Merged
Conversation
Fixed this in zed-industries/zed#54011. |
Contributor
|
@sunshowers thanks so much! |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Thanks to some back and forth with the rust-analyzer team rust-lang/rust-analyzer#21137 we can now use nextest as the test backend for the
Run TestandRun Testsbuttons in VS Code. You'll need the pre-release version of rust-analyzer, but I think we all use that.Runnables aren't yet supported in Zed IIUC, so I didn't change any setting there.
See rust-lang/rust-analyzer#21137 (comment) for some examples of how I use this.
In particular, it is fantastic for
Run Testson a group of tests that access R and must run in separate processes via nextest. Previously, it you hit that shinyRun Testsbutton then you'd footgun yourself and hang one of the R sessions.