Skip to content
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

Make it easier to have unit tests in VSCode packages #1541

Merged

Conversation

pokey
Copy link
Member

@pokey pokey commented Jun 19, 2023

Introduces a new convention for tests that end with .vscode.test.ts must run within VSCode; other tests can be run as unit tests outside of VSCode. This makes it easier to add unit tests within packages such as cursorless-vscode. Just because a package is designed to be used with VSCode doesn't mean that all of its tests should have to be run within a VSCode context. It might (and should!) have support code that consists of pure functions with no dependencies.

Checklist

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this wasn't used anywhere

@pokey pokey marked this pull request as ready for review June 19, 2023 14:38
@pokey pokey force-pushed the pokey/make-it-easier-to-have-unit-tests-in-vscode-packages branch from 9a6c0f3 to 40876ec Compare June 19, 2023 14:42
@pokey pokey requested a review from AndreasArvidsson June 19, 2023 14:43
@pokey pokey added this pull request to the merge queue Jun 19, 2023
Merged via the queue into main with commit 95f605b Jun 19, 2023
@pokey pokey deleted the pokey/make-it-easier-to-have-unit-tests-in-vscode-packages branch June 19, 2023 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants