Add debugging support for Jest integration tests#1793
Merged
koesie10 merged 1 commit intojest-migration/integration-testsfrom Nov 25, 2022
Merged
Add debugging support for Jest integration tests#1793koesie10 merged 1 commit intojest-migration/integration-testsfrom
koesie10 merged 1 commit intojest-migration/integration-testsfrom
Conversation
Since we are launching a completely different process for the extension tests than the process that is launched by VSCode, we need to add some special handling for the debugging. This will let the extension host/VSCode expose a debugging port, which VSCode will then connect to. This is "less desirable than letting the bootloader do its thing", but a packaged VSCode application does not allow using the bootloader (`NODE_OPTIONS`=`--require=...`). Therefore, we have to fallback to this option. See: https://github.com/microsoft/vscode-js-debug/blob/47c60558ec31902f42c255abb9b460078df02f9d/src/configuration.ts#L405-L411
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Since we are launching a completely different process for the extension tests than the process that is launched by VSCode, we need to add some special handling for the debugging.
This will let the extension host/VSCode expose a debugging port, which VSCode will then connect to. This is "less desirable than letting the bootloader do its thing", but a packaged VSCode application does not allow using the bootloader (
NODE_OPTIONS=--require=...). Therefore, we have to fallback to this option.See: https://github.com/microsoft/vscode-js-debug/blob/47c60558ec31902f42c255abb9b460078df02f9d/src/configuration.ts#L405-L411
Checklist
ready-for-doc-reviewlabel there.