Migrate test running to the new vscode-test-cli#4079
Merged
vinistock merged 1 commit intoApr 28, 2026
Conversation
Member
Author
How to use the Graphite Merge QueueAdd the label graphite-merge to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
f16d17c to
87b62ac
Compare
vinistock
commented
Apr 24, 2026
03bb5d2 to
3fdb680
Compare
vinistock
commented
Apr 24, 2026
b13d63d to
dfe472f
Compare
3fdb680 to
cb6f545
Compare
rafaelfranca
approved these changes
Apr 27, 2026
cb6f545 to
522724d
Compare
dfe472f to
5e50d9b
Compare
Merge activity
|
5e50d9b to
cfc4287
Compare
graphite-app Bot
pushed a commit
that referenced
this pull request
Apr 27, 2026
### Motivation The test setup for VS Code extensions has changed a bit since the time when we created the Ruby LSP. This PR migrates us to the latest recommendations. ### Implementation Basically, we now use `@vscode/test-cli` which allows us to configure our tests in a declarative way. This allows us to get rid of some boiler plate files like `index.ts`. The other side of this is that we can now run tests through the test explorer panel, allowing us to easily run a single example at a time. Much better DX.
522724d to
f7ee099
Compare
### Motivation The test setup for VS Code extensions has changed a bit since the time when we created the Ruby LSP. This PR migrates us to the latest recommendations. ### Implementation Basically, we now use `@vscode/test-cli` which allows us to configure our tests in a declarative way. This allows us to get rid of some boiler plate files like `index.ts`. The other side of this is that we can now run tests through the test explorer panel, allowing us to easily run a single example at a time. Much better DX.
f7ee099 to
3bd3365
Compare
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 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.

Motivation
The test setup for VS Code extensions has changed a bit since the time when we created the Ruby LSP. This PR migrates us to the latest recommendations.
Implementation
Basically, we now use
@vscode/test-cliwhich allows us to configure our tests in a declarative way. This allows us to get rid of some boiler plate files likeindex.ts.The other side of this is that we can now run tests through the test explorer panel, allowing us to easily run a single example at a time. Much better DX.