vscode/test/integration/browser
Benjamin Pasero 789c320a1c
Replace mkdirp with fs.mkdirSync(path, { recursive: true }) (#228017)
* Replace mkdirp with fs.mkdirSync(path, { recursive: true })
(fix #227931)

* compile
2024-09-09 22:43:29 -07:00
..
src chore: update to electron 30 (#215406) 2024-07-09 14:33:22 +09:00
.gitignore
README.md feat: switch to npm as default package manager (#226927) 2024-09-06 22:18:02 +09:00
package-lock.json Replace mkdirp with fs.mkdirSync(path, { recursive: true }) (#228017) 2024-09-09 22:43:29 -07:00
package.json Replace mkdirp with fs.mkdirSync(path, { recursive: true }) (#228017) 2024-09-09 22:43:29 -07:00
tsconfig.json Fix some always true/false errors in codebase (#223359) 2024-07-30 15:37:27 -07:00

README.md

Integration test

Compile

Make sure to run the following commands to compile and install dependencies:

cd test/integration/browser
npm i
npm run compile

Run (inside Electron)

scripts/test-integration.[sh|bat]

All integration tests run in an Electron instance. You can specify to run the tests against a real build by setting the environment variables INTEGRATION_TEST_ELECTRON_PATH and VSCODE_REMOTE_SERVER_PATH (if you want to include remote tests).

Run (inside browser)

scripts/test-web-integration.[sh|bat] --browser [chromium|webkit] [--debug]

All integration tests run in a browser instance as specified by the command line arguments.

Add the --debug flag to see a browser window with the tests running.

Note: you can enable verbose logging of playwright library by setting a DEBUG environment variable before running the tests (https://playwright.dev/docs/debug#verbose-api-logs)

Debug

All integration tests can be run and debugged from within VSCode (both Electron and Web) simply by selecting the related launch configuration and running them.