-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Add docs on how to test debug adapters in a CI environment #101
Comments
I saw that there is some documentation on testing normal extensions, but nothing about debug adapters. @weinand some help maybe? Testing all possible constellations manually on all OS is a pain. I had some thoughts on this issue |
@felixfbecker A test suite for debug adapters is in the works. Please see the January iteration plan: microsoft/vscode#1826 |
@felixfbecker you can find a first version of the test suite here: https://github.com/Microsoft/vscode-node-debug/blob/master/src/tests The DebugClient.ts defines the API and will be moved (together with ProtocolClient.ts) into the npm module soon. adapter.test.ts contains a first batch of tests. More to come... |
@weinand This looks very promising, when will it get included in the NPM package? |
@felixfbecker soon, I hope. Need to find some time to write more tests to exercise the API.... |
This issue has been very quiet and looks like @felixfbecker is happy with the tests added to the vscode-node-debug repo. Closing |
In the mock-debug adapter for example is a test folder included with a dummy mocha test. But how can one actually test VS Code extensions and debug adapters? Especially with something like Travis CI.
The text was updated successfully, but these errors were encountered: