microsoft / vscode-test

Testing utility for VS Code extensions

microsoft/vscode-test Issues

Error: Failed to download and unzip VS Code 1.90.2
Closed 25 days ago1
dbus errors during VS Code installation
Closed a month ago3
would be great to have a customizable cache path
Closed 2 months ago1
`--install-extension` flag not working on Windows with Node 20.12.2
Closed 3 months ago4
`extensionPaths` to load an array of extensions easily
Closed 2 months ago1
Extension installation is broken on Windows
Closed 2 months ago4
Testing does not insert correct env/Script to PATH env var in windows.
Closed 3 months ago1
Developing tests in a different directory/repository
Updated 3 months ago2
Downloading vscode aborted when retrying
Closed 3 months ago4
Error: @vscode/test-electron request timeout out after 15000ms
Closed 4 months ago3
github actions: Failed to get win32 version
Closed 5 months ago1
Extension installation fails with EPERM on windows when running with vscode-test
Updated 5 months ago9
Unable to use global fixtures.
Closed 5 months ago3
error when running on WSL2
Closed 6 months ago1
MacOS Electron EACCES error when using `runTests`
Closed 7 months ago11
Fails silently when globbing files
Closed a year ago1
Incorrect installation path when using `downloadAndUnzipVSCode` in versions 1.85.0 and above
Closed 6 months ago3
Fails to run if cached: Error IPC handle is longer than 103 chars.
Updated 7 months ago1
Mocha parallel mode issue
Closed 7 months ago1
ENOENT Error Running Tests with VSCode 1.85.1
Closed 7 months ago5
VS Code executable not found after downloading it
Closed 8 months ago25
Failed to download and unzip VS Code 1.84.2
Closed 8 months ago2
run tests with --watch
Closed 9 months ago1
Error: connect ENOTSOCK on OSX
Closed 2 years ago2
Error when downloading VS Code
Closed 9 months ago7
Sample should be updated to match generator template
Updated 10 months ago
Error: spawn UNKNOWN after downloading VSCode
Closed 10 months ago2
cannnot run with github actions
Closed a year ago2
Failed to run test in vscode@1.79.0 but work on 1.78.2
Closed a year ago5
typo CHANGELOG.md is 2023 year
Updated a year ago
Test_C#
Closed a year ago
Controlling activationEvents when testing extensions?
Closed a year ago1
Running tests with a bundler should be easier
Updated a year ago5
Clarification on the extensionTestsPath run signature
Closed a year ago3
Have a launch.json that uses the downloaded vscode, not the currently running one
Updated a year ago
startDebugging always fails with "DialogService: refused to show dialog in tests."
Closed a year ago5
Possibly misleading comment suggesting importing the extension
Updated a year ago6
Dynamically change main entry point in package.json when running tests
Closed 2 years ago4
Be able to grab an insiders build based on the specified version (if appropriate)
Closed a year ago
Add a check to make sure an "existing installation" actually is fully available and works
Closed a year ago3
Move away from unzipper which is unmaintained
Closed a year ago
Dependency licensing issue: buffers
Closed a year ago
`runTests` fails to attach to the spawned vscode instance if no extensions are installed
Closed a year ago2
SFV
Closed a year ago1
Using custom setup to install extensions, tests are run in an instance without the extensions installed
Closed a year ago3
Custom setup not working as documented
Closed 2 years ago
2.2.1 requires node >= 16.0 but the documentation still says 12
Closed 2 years ago2
Add support for executing commands
Closed 2 years ago2
VSCode Test Runner does not install or run correctly in Azure Dev Ops Builds
Closed 2 years ago1
Unable to activate extension with `extensionDependencies`
Closed 2 years ago2