ckaczor/azuredatastudio
1
0
Fork 0
mirror of https://github.com/ckaczor/azuredatastudio.git synced 2026-02-17 02:51:36 -05:00
Code Issues Packages Projects Releases Wiki Activity

Update readme.md (#4907)

Browse Source
This commit is contained in:
Alan Ren
2019-04-08 16:25:53 -07:00
committed by GitHub
parent ada0966832
commit 5dc6a39652
1 changed files with 21 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

42
extensions/integration-tests/readme.md
View File

@@ -1,33 +1,31 @@
#Integration tests ## Integration tests
This integration-tests suite is based on the extension testing feature provided by VS Code, We can use this for: The integration-tests suite is based on the extension testing feature provided by VS Code, We can use this for:
a. Commands for setting up the environment for feature testing. * Commands for setting up the environment for feature testing.
b. 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) * 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)
extensionInstallers folder: copy the VISX installers for the extensions we would like to run the tests with. ##### Folders
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 * 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
ADS will be launched using new temp folders: extension folder and data folder so that your local dev environment won't be changed. 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: ## How to run the test
1. In the build pipeline: 1. 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. 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.
2. Local environment: 2. Local environment:
a. 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) 1. 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)
b. navigate to this folder and then run 'node setEnvironmentVariables.js' 2. navigate to this folder and then run 'node setEnvironmentVariables.js', there are different options, by default VSCode will be opened.
there are different options, by default VSCode will be opened. 1. Terminal(Mac)/CMD(Windows): node setEnvironmentVariables.js Terminal
1. Terminal(Mac)/CMD(Windows): node setEnvironmentVariables.js Terminal 2. Git-Bash on Windows: node setEnvironmentVariables.js BashWin
2. Git-Bash on Windows: node setEnvironmentVariables.js BashWin 3. Follow the instructions in the window: you will be prompted to login to azure portal.
c. follow the instructions in the window: you will be prompted to login to azure portal. 4. A new window will be opened based on your selection and the new window will have the required environment variables set.
d. a new window will be opened based on your selection and the new window will have the required environment variables set. 5. In the new window navigate to the scripts folder and run sql-test-integration.bat or sql-test-integration.sh based on your environment.
e. in the new window navigate to the scripts folder and run sql-test-integration.bat or sql-test-integration.sh based on your environment.
## 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.
#UI automation testing: ## How to run the test
the ADS 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.
##How to run the test:
1. In the build pipeline: 1. In the build pipeline:
The smoke 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. The smoke 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.