Auto discover Rust tests #50
Draft
Conversation
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
rust-analyzer can tell VS Code which tests exist. But in combination with Bazel this is currently hardly useful. Tests can be executed, but not debugged, which mostly nullifies having the tests in VS Code.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
rust-analyzer can tell Visual Studio Code which tests exist. But in combination with Bazel this is currently hardly useful. Tests can be executed, but not debugged, which mostly nullifies having the tests in Visual Studio Code.
Until we have figured out how to debug tests as well, I see no point in merging this and this pull request acts more like documentation.
Related to #38