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

[Feature] Figure out extension testing best practices and create projen component for it #6

Closed
MarkMcCulloh opened this issue Dec 5, 2021 · 5 comments
Labels
backlog enhancement New feature or request stale

Comments

@MarkMcCulloh
Copy link
Owner

Is your feature request related to a problem? Please describe.
From the default template, extension testing is done with mocha. Considering projen leans more towards jest, it may be nice to explore that option.

Describe the solution you'd like
Find the best way to test this thing and make sure it's included in the base projen project type.

@MarkMcCulloh MarkMcCulloh changed the title [Feature] Figure out extension testing best practive and create projen component for it [Feature] Figure out extension testing best practices and create projen component for it Dec 5, 2021
@MarkMcCulloh MarkMcCulloh added the enhancement New feature or request label Dec 5, 2021
@MarkMcCulloh
Copy link
Owner Author

Thoughts so far:

I think E2E testing is not worth the headache. This of course depends on the complexity and risk associated with the extension. Unfortunately, the mocking needs some work too, but not as much. I think when the VSCodeExtension project type is added to projen, it should default to assuming unit tests are focused. At this point, need to look into what exists to help out with that.

Check out microsoft/vscode#94746

@github-actions
Copy link

github-actions bot commented Apr 7, 2022

This issue is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon.

@github-actions github-actions bot added the stale label Apr 7, 2022
@github-actions
Copy link

Closing this issue as it hasn't seen activity for a while. Please add a comment @mentioning a maintainer to reopen.

@github-actions
Copy link

github-actions bot commented Jul 7, 2022

This issue is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon.

@github-actions github-actions bot added the stale label Jul 7, 2022
@github-actions
Copy link

Closing this issue as it hasn't seen activity for a while. Please add a comment @mentioning a maintainer to reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog enhancement New feature or request stale
Projects
None yet
Development

No branches or pull requests

1 participant