Add basic e2e tests for user scripts #136
Comments
PEZ
added a commit
that referenced
this issue
Jan 5, 2023
* Add smoke test for user-activate * Add JS example script to default user scripts content Addressing #136 TODO: * [ ] Add more smoke tests * [ ] Handle new my-lib location somehow
PEZ
added a commit
that referenced
this issue
Jan 6, 2023
* Add configurable user scripts location via env var * Add smoke test for user-activate * Add JS example script to default user scripts content Fixes #136 TODO: * [ ] Add more smoke tests * [ ] Handle new my-lib location somehow * Make user JS scripts reload when run * Create user example script exports work * Add tests for running user scripts * Consolidate test files some * Add test for reloading js scripts * Add check for minimum passed assertions Fixes #138 * Only create getting started user content if activate is missing Fixes #139 * Add test run launch config * Open extension host in workspace 1 folder by default
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Like we have for workspace scripts. I noticed while adding JS scripts support that it is entirely possible to make things work for workspace scripts, and fail for user scripts. 😄
The text was updated successfully, but these errors were encountered: