Add infrastructure for VS Code extension tests - #757
Conversation
juliasilge
changed the title
juliasilge
changed the title
| runBuild({ | ||
| const testBuildOptions = { | ||
| entryPoints: testFiles, | ||
| outdir: 'test-out', |
There was a problem hiding this comment.
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.
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 |
juliasilge
changed the title
|
I did it! 🎉 I have one very simple test, and tools to run that both locally and in CI. |
cscheid
left a comment
cscheid
left a comment
There was a problem hiding this comment.
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 |
3 participants
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