Run scope tests as unit test outside of vscode#3210
Merged
AndreasArvidsson merged 15 commits intomainfrom Mar 11, 2026
Merged
Conversation
AndreasArvidsson
requested review from
a team,
fidgetingbits and
saidelike
as code owners
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
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.
We're getting quite a lot of scope test by now and running all of them inside of the yes code is very slow. This updates allow us to run the scope test as unit tests outside of the vscode. It also refactors the test workflow so all unit tests run outside of the editors.
As a side defect of running into quite a lot of bugs for this implementation I added better error messages, missing error logging, missing types etc in various files.