unittest

[YongseopKim]

cmd가 실제로 필요한 테스트와, 아닌 테스트로 나뉘어야 함

[YongseopKim]

--grep 'integrated'
--grep 'mockup'

[YongseopKim]

mocha: https://mochajs.org chai: https://www.chaijs.com

[YongseopKim]

one-import-bcq has one-import-onnx

[YongseopKim]

ui와 관련된 test는 제외 positive tests만 BuilderCfgFile: 대다수가 private

[YongseopKim]

test bdd로 두번 임포트하는 경우

[YongseopKim]

리드미 작성

[YongseopKim]

nvm

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | bash
source ~/.zshrc

nvm install 16.14.0
nvm use 16.14.0

npm 8.3.1

[YongseopKim]

Extension Development Host

• full access to the VS Code API

# - Launches VS Code Extension Host
code \
--extensionDevelopmentPath=<EXTENSION-ROOT-PATH> \ # - Loads the extension at <EXTENSION-ROOT-PATH>
--extensionTestsPath=<TEST-RUNNER-SCRIPT-PATH> # - Executes the test runner script at <TEST-RUNNER-SCRIPT-PATH>

The test script (runTest.ts)

• uses the @vscode/test-electron API to simplify the process of downloading, unzipping, and launching VS Code with extension test parameters
• --extensionTestsPath points to the test runner script

The test runner script (index.ts)

• programmatically runs the test suite

Because of VS Code's limitation, if you are using VS Code stable release and try to run the integration test on CLI, it will throw an error:

Running extension tests from the command line is currently only supported if no other instance of Code is running.

In general if you run extension tests from CLI, the version the tests run with cannot be running already. As a workaround, you can run the tests in VS Code Stable and use VS Code Insiders for development. As long as you are not running the tests from CLI in VS Code Insiders but in VS Code Stable, this setup will work fine.