Issue with Opening Default Folder in VSCode Instance Using vscode-extension-tester
typescript
Ethan JacksonI am attempting to use the vscode-extension-tester from this tutorial: https://github.com/redhat-developer/vscode-extension-tester-example. However, I am unable to set an open default folder in my VSCode instance.
Answer
It seems like there's no equivalent of setting a default folder in the vscode/test-electron environment using .vscode-test.mjs or a default workspaceFolder for the vscode-extension-tester.
What I have tried:
- Using vscode.openFolder command in test.ts:
import \* as vscode from 'vscode';
import \* as path from 'path';
let uri = vscode.Uri.file('/some/path/to/folder');
let success = await vscode.commands.executeCommand('vscode.openFolder', uri);
- The output :
Loading mocha configuration from PATH\\.mocharc.js
Error: Cannot find module 'vscode'
Require stack:
\- PATH\\out\\ui-test\\CreateProject.test.js
\- PATH\\node_modules\\mocha\\lib\\mocha.js
\- PATH\\node_modules\\mocha\\index.js
\- PATH\\node_modules\\vscode-extension-tester\\out\\suite\\runner.js
\- PATH\\node_modules\\vscode-extension-tester\\out\\util\\codeUtil.js
\- PATH\\node_modules\\vscode-extension-tester\\out\\extester.js
\- PATH\\node_modules\\vscode-extension-tester\\out\\cli.js
Additionally, the VSCode instance doesn't open. Even when I add VSCode to the devDependencies, there seems to be an error and it doesn't work.
- Using VSBrowser to open folder:
import {VSBrowser} from 'vscode-extension-tester';
await VSBrowser.instance.openResources('/some/path/to/folder');
- The output :
Error: spawnSync cmd.exe ENOENT
