Closed MarkMcCulloh closed 2 years ago
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.
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.