mirror of
https://github.com/ckaczor/azuredatastudio.git
synced 2026-01-14 01:25:37 -05:00
2781279644
* Add notebook editor Introduce notebook editor component to allow for separate notebook displays in order to accomodate notebook views * Localize notebook views configuration title * Refactor view mode and remove the views configuration while it is unused * Only fire view mode changed event when the value has been changed * Remove notebook views contribution * Add metadata capabilities * Notebook views definitions * Add notebook views models * Views test * Rename type arguments * Additional tests * Fix unused import * Notebook views changes * Add notebookviews.css * Update notebookViewModel.ts * Add cell toolbar styles * Upgrade gridstack * Add gridstack styles * Remove ununsed references These are part of the next PR and not available yet * Remove gridstack static file * Add gridstack as a module in the electron unit tests * Spacing fixes * Add copyright notice * Remove commented code * Spacing fixes in notebook styles * Move handle svg to image * Add typing for gridstack * Move notebook styles to file * Rename selector constant * Rename grid css file * Add nb-grid-stack class to views grid * Cell toolbar style adjustments * Remove unused imports * Update .eslintrc.json * Fix outdated instantiation of LabeledMenuItemActionItem * Address feedback * Fix from update to main
Unit Tests
Run (inside Electron)
./scripts/test.[sh|bat]
All unit tests are run inside a electron-browser environment which access to DOM and Nodejs api. This is the closest to the environment in which VS Code itself ships. Notes:
- use the
--debugto see an electron window with dev tools which allows for debugging - to run only a subset of tests use the
--runor--globoptions
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.htmlinside a browser and use the?m=<amd_module>-query to specify what AMD module to load, e.gfile:///Users/jrieken/Code/vscode/test/unit/browser/renderer.html?m=vs/base/test/common/strings.testruns all tests fromstrings.test.ts - to run only a subset of tests use the
--runor--globoptions
Run (with node)
yarn run mocha --run src/vs/editor/test/browser/controller/cursor.test.ts
Coverage
The following command will create a coverage folder at the root of the workspace:
OS X and Linux
./scripts/test.sh --coverage
Windows
scripts\test --coverage