-
Notifications
You must be signed in to change notification settings - Fork 41
Add infrastructure for VS Code extension tests #757
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
runBuild({ | ||
const testBuildOptions = { | ||
entryPoints: testFiles, | ||
outdir: 'test-out', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This creates the test .js
files in the directory where we can tell the vscode-test
cli where to find them.
|
||
export default defineConfig([ | ||
{ | ||
files: 'test-out/*.test.js', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is where we tell the vscode-test
cli where to find the files.
As of my writing now, to compile and run the tests:
|
Now it's just |
I did it! 🎉 I have one very simple test, and tools to run that both locally and in CI. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very excited about this PR!
Everything looks good from what I can tell. It also seems very low risk to just merge this, given it doesn't really interact with the other parts of the code base. If the CI action acts up, we can just disable the workflow.
Tested |
We want to get some first infrastructure set up here, so we can start writing extension level tests: https://code.visualstudio.com/api/working-with-extensions/testing-extension