-
Notifications
You must be signed in to change notification settings - Fork 1
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
Comments
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 |
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. |
Closing this issue as it hasn't seen activity for a while. Please add a comment @mentioning a maintainer to reopen. |
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. |
Closing this issue as it hasn't seen activity for a while. Please add a comment @mentioning a maintainer to reopen. |
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.
The text was updated successfully, but these errors were encountered: