maxmustermann/vscode
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
vscode/test
History
Johannes Rieken d288521f32 update test readme
2020-02-07 16:49:49 +01:00
..
automation tests - browser tests to go through new log service 2020-02-07 16:22:10 +01:00
integration/browser test - fix help output for integration too 2020-02-07 16:48:46 +01:00
smoke test - convert web integration to TS 2020-02-07 12:41:12 +01:00
ui tests - add a UI folder for manual UI tests 2020-02-07 10:17:49 +01:00
unit add help printing 2020-02-07 16:20:09 +01:00
cgmanifest.json rename isOnlyDevelopmentDependency to developmentDependency 2018-11-21 16:17:52 +01:00
mocha.opts
README.md update test readme 2020-02-07 16:49:49 +01:00

README.md

VSCode Tests

Contents

This folder contains the various test runners for VSCode. Please refer to the documentation within for how to run them:

  • unit: our suite of unit tests
  • integration: our suite of API tests
  • smoke: our suite of automated UI tests
  • ui: our suite of manual UI tests

Browser Unit Tests

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 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