84607a2fe2
* Fix some always true/false errors in codebase Testing out latest TS nightly that can identify when an expression is always true/false. This caught a few likely coding mistakes in our codebase Unsure about the intent in some of these cases but I've tried my best to understand them. Pinging relevant code owners for the confusing cases * Bump TS version * Fix unreachable in build scripts * Bump versions * restore intent * Revert package.json change * Fixing a few new layer checker errors These are global in node now * Skip lib check in integration project * One more skiplibcheck * More skip lib --------- Co-authored-by: Benjamin Pasero <benjamin.pasero@gmail.com>
Integration test
Compile
Make sure to run the following commands to compile and install dependencies:
yarn --cwd test/integration/browser
yarn --cwd test/integration/browser 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.