vscode-test@1.0.1 vscodeExecutablePath issue

[Eskibear]

To solve issue #29 , you make it point it to VSCode CLI. Now it's ok to install extensions but fail to run tests.

// Here the path should point to Electron, otherwise it won't run the test. 
 await runTests({ vscodeExecutablePath, extensionDevelopmentPath, extensionTestsPath });

[octref]

I published 1.0.2 to temporarily revert the change. I'll work on a new fix.

[Eskibear]

may I ask when will the new fix be available?

[octref]

Would a change like this work for you?

Before:

export async function downloadAndUnzipVSCode(version?: DownloadVersion): Promise<string> {}

After:

export async function downloadAndUnzipVSCode(version?: DownloadVersion): Promise<{
	vscodeExecutablePath: string,
	vscodeCLIPath: string
}> {}

[octref]

Current issues is:

• Launching process through CLI won't launch tests properly
• Launching process through Electron won't handle args handled in cli

So the new API would be:

• For beginners / simple usage, still call runTests with the current API. I'll expand launchArgs's documentation to say which args aren't accepted.
• For advanced usage, users call downloadAndUnzipVSCode to get the two paths. They still need to pass vscodeExecutablePath to runTests, but they can run CLI process with vscodeCLIPath as well.

[Eskibear]

Thanks in advance. The new API can unblock me from the current problem. The request is actually to provide a way to know the CLI path, in order to install prerequisite extensions.

BTW, the document for vscode-test is pointing to a dead end, which is harming VS Code's reputation.

[octref]

To not break backward-compatibility, I decided to export another function called resolveCliPathFromVSCodeExecutablePath. Sample usage here: https://github.com/microsoft/vscode-test/blob/master/sample/test/runTest.ts#L68-L75

[octref]

Published in 1.1.0.