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

Automated testing of debugger and coverage reports #1822

Open
cspotcode opened this issue Jul 2, 2022 · 1 comment
Open

Automated testing of debugger and coverage reports #1822

cspotcode opened this issue Jul 2, 2022 · 1 comment

Comments

@cspotcode
Copy link
Collaborator

cspotcode commented Jul 2, 2022

Motivated by #1769, #1797 and #1790

Automated testing will help ensure I understand if/when/how these use-cases are affected by changes to ts-node.

Automated testing of a debugger, in particular, will be tricky. I have no idea how to automatically test VSCode, though I bet there's a way, since they do seem to have good testing infrastructure. It's a complex beast, though.

See also: this comment mentions a c8 use-case to test: #1821 (comment)

@timvahlbrock
Copy link

In case this issue is still relevant: Maybe you might want to take a look at @vscode/debugadapter-testsupport. It is used to perform automated test on the javascript debugger built in to VSCode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants