Why
The Python sidecar is well tested, but the TypeScript extension has no automated tests yet. @vscode/test-electron + @vscode/test-cli would let CI exercise activation, the sidecar-lifecycle wiring, and command registration.
What to do
- Add the vscode-test harness under
extension/, plus one activation smoke test (extension activates, the docchat.* commands are registered).
- Wire a
test script and a CI step into the extension job in .github/workflows/ci.yml.
Acceptance criteria
npm test runs the vscode-test suite headlessly; the new CI step is green.
Pointers
extension/src/extension.ts (activate/deactivate), extension/package.json (contributes.commands).
Why
The Python sidecar is well tested, but the TypeScript extension has no automated tests yet.
@vscode/test-electron+@vscode/test-cliwould let CI exercise activation, the sidecar-lifecycle wiring, and command registration.What to do
extension/, plus one activation smoke test (extension activates, thedocchat.*commands are registered).testscript and a CI step into theextensionjob in.github/workflows/ci.yml.Acceptance criteria
npm testruns the vscode-test suite headlessly; the new CI step is green.Pointers
extension/src/extension.ts(activate/deactivate),extension/package.json(contributes.commands).