Closes #1092: Add launch configuration for debugging tests #1115
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue This PR Addresses
Closes #1092
Type of Change
Description
This modifies
launch.json
to include test debugging. With the new settings, it's possible to choose between running and debugging one test (the one opened in the editor) or all of them (run sequentially like when runningnpm run test
".Note:
Running tests using VSCode debugger shows an
illegal access
error after completing all the tests.More specifically:
node::inspector::Agent::ToggleAsyncHook Cannot toggle Inspector's AsyncHook, please report this.
This is a
nodejs
error, and according to their repo, it'll be fix in the next release this month (September 2020).More info about this issue here.
Checklist