If running extension tests from CLI, the VS Code version the tests run with cannot be running already. As a workaround, VS Code Insiders should be used for test development, so that tests may run in VS Code Stable.
For more information regarding this limitation, refer to using insiders version for extension development.
Tests are currently only setup to run locally.
- Install root dependencies
From the root of the repo, install all of the build dependencies:
[sudo] yarn- Compile the extension and tests by running:
gulp buildor watch for changes in the tests by running:
gulp watch-testsTo run tests, the following options can be used:
-
Using Playwright Test for VSCode:
- Install the
Playwright Test for VSCodeextension in VS code. - Run tests with a single click
Note: If you don't see any tests appearing in the Test Explorer view, like in the image, then you'll need to run them from the terminal first to get them to appear. Please refer to option 2.
- Install the
.
-
Setup environment variables in the
test\e2efolder- Create a
.envfile - Add the variables that you want based on the .env.example
- Example:
VS_CODE_VERSION_NAME=stable SERVER_NAME=(localdb)\MSSqlLocalDb AUTHENTICATION_TYPE=Integrated PROFILE_NAME=test-server
- Create a
-
To run tests from the command line execute the following command from the root:
npx playwright test
The tests will automatically appear in the Test Explorer view after running them once, and green run icons will appear to the left of line numbers in the editor, like this:
