mirror of https://github.com/microsoft/vscode.git synced 2025-12-25 20:57:12 +00:00

Files

Johannes Rieken 2d97803568 add ListenerRefusalError and ListenerLeakError which get logged when listener thresholds are exceeded. (#212900 )

* add `ListenerRefusalError` and `ListenerLeakError` which get logged when listener thresholds are exceeded.

The `stack` property of these errors will point towards the most frequent listener and how often it is used. If that's a high number there is a leak (same listener is added over and over again), if that's a low number there might be a conceptual flaw that an emitter is simply too prominent.

* rightfully don't use Error.captureStackTrace (v8/nodejs only)

2024-05-16 08:29:17 -07:00

browser

eng: support runGlob in browser unit tests (#199979 )

2023-12-04 12:14:25 -08:00

electron

add ListenerRefusalError and ListenerLeakError which get logged when listener thresholds are exceeded. (#212900 )

2024-05-16 08:29:17 -07:00

node

testing: more out-of-editor refinements (#201834 )

2024-01-04 21:22:46 +01:00

analyzeSnapshot.js

eng: add assertHeap method for memory assertions (#198334 )

2023-11-15 10:41:22 -08:00

assert.js

…

coverage.js

testing: more out-of-editor refinements (#201834 )

2024-01-04 21:22:46 +01:00

fullJsonStreamReporter.js

fix incomplete coverage reports on macos (#212639 )

2024-05-13 15:27:00 -07:00

README.md

…

reporter.js

…

README.md

Unit Tests

Run (inside Electron)

./scripts/test.[sh|bat]

All unit tests are run inside a Electron renderer environment which access to DOM and Nodejs api. This is the closest to the environment in which VS Code itself ships. Notes:

use the --debug to see an electron window with dev tools which allows for debugging
to run only a subset of tests use the --run or --glob options
use yarn watch to automatically compile changes

For instance, ./scripts/test.sh --debug --glob **/extHost*.test.js runs all tests from extHost-files and enables you to debug them.

Run (inside browser)

yarn test-browser --browser webkit --browser chromium

Unit tests from layers common and browser are run inside chromium, webkit, and (soon'ish) firefox (using playwright). This complements our electron-based unit test runner and adds more coverage of supported platforms. Notes:

these tests are part of the continuous build, that means you might have test failures that only happen with webkit on windows or chromium on linux
you can run these tests locally via yarn test-browser --browser chromium --browser webkit
to debug, open <vscode>/test/unit/browser/renderer.html inside a browser and use the ?m=<amd_module>-query to specify what AMD module to load, e.g file:///Users/jrieken/Code/vscode/test/unit/browser/renderer.html?m=vs/base/test/common/strings.test runs all tests from strings.test.ts
to run only a subset of tests use the --run or --glob options

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)

Run (with node)

yarn test-node --run src/vs/editor/test/browser/controller/cursor.test.ts

Coverage

The following command will create a coverage folder in the .build folder at the root of the workspace:

OS X and Linux

./scripts/test.sh --coverage

Windows

scripts\test --coverage