Add integration test infrastructure and dev container#153
Open
Add integration test infrastructure and dev container#153
Conversation
|
Coverage after merging feature/integration-tests-dev-container into master will be
Coverage Report |
brynrhodes
reviewed
Mar 28, 2026
Member
brynrhodes
left a comment
There was a problem hiding this comment.
integration tests work, npm test still works, but I'm getting an error trying to reopen in container (gets an error on trying to add the gid saying it already exists)
raleigh-g-thompson
requested changes
Mar 29, 2026
Contributor
raleigh-g-thompson
left a comment
There was a problem hiding this comment.
Please rebase on to v0.9.0.
…ubuntu" user/group to "vscode" so that USER vscode resolves correctly
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.
Summary
Motivation
Previously there were no end-to-end tests covering the boundary between the extension and the language server. Each repo was tested in isolation with mocked interfaces. This gap allowed issues like compiler options not being applied to go undetected.
Test plan