mirror of
https://github.com/ckaczor/azuredatastudio.git
synced 2026-01-19 09:35:36 -05:00
6e6649d006
* move * add inital test; need basic sqllite connection * before sqlite * sqlite * add smoke tests * working tests * fix app names * fix quick open * fix smoke tests * add win32 smoke tests * fix smoke test * fix win32 smoke * no continue * continue on error * add vscode smokes * remove vscode tests * continue on error * allow sqlite to use relative paths * add linux smoke tests * fix build files * use dispatch instead of select * fix linux build again * fix darwin * get select working * try and use screen shots * screen shots * remove smoke tests linux * try vscodes sqlite * fix compile * fix webpack * fix deps * try this again * try force a rebuild * try npm rebuild * add sqlite to be rebuilt * distro * try vscode sqlite again * revert changes to driver and simplify edits * fix compile * fix imports * move sqlite out * remove unneeded change * add extensions path * fix web tests * no continue on error
Integration tests
The integration-tests suite is based on the extension testing feature provided by VS Code, We can use this for:
- Commands for setting up the environment for feature testing.
- Adding test cases that do not need UI interaction or the test scenarios not supported by the UI automation framework (e.g. object explorer context menu – not html based)
Folders
- extensionInstallers folder: Copy the VISX installers for the extensions we would like to run the tests with.
- src folder: This is where the test file for features should be added, name the file like this: feature.test.ts. e.g. objectExplorer.test.ts
UI automation testing
The UI automation test cases should be added under $root/test/smoke/src/sql folder. Each feature should create its own folder and add 2 files, one for accessing the feature and the other for the test cases. For example: objectExplorer.ts and objectExplorer.test.ts. only tested on Windows for now.
For both Smoke test and Integration test, ADS will be launched using new temp folders: extension folder and data folder so that your local dev environment won't be changed.
How to run the test
-
In the build pipeline: The integration test suite has been added to ADS windows pipeline to run the test and report the results, you can find the test results under the test tab.
-
Local environment:
- open a terminal window/command line window. (When testing on Mac we found some issue with VSCode scenario, you might have to close VSCode before running the command)
- navigate to this folder and then run 'node setEnvironmentVariables.js', there are different options, by default VSCode will be opened.
- Terminal(Mac)/CMD(Windows): node setEnvironmentVariables.js Terminal
- Git-Bash on Windows: node setEnvironmentVariables.js BashWin
- Follow the instructions in the window: you will be prompted to login to azure portal.
- A new window will be opened based on your selection and the new window will have the required environment variables set.
- Run the Test:
- For Integration Test: in the new window navigate to the scripts folder and run sql-test-integration.bat or sql-test-integration.sh based on your environment.
- Smoke Test can be launched in 2 ways:
- In the new window navigate to the test/smoke folder and run: node smoke/index.js
- Or, In a VSCode window opened by step above, open AzureDataStudio folder and then select the 'Launch Smoke Test' option.
How to debug the tests
- Set the debug target to
Attach to Extension Host - Run the script to start the tests
- Wait for the Window to reload (it does this after installing and activating the extensions)
- Run the debug target - it should now attach to the Extension Host process and hit breakpoints set in the integration tests