mrva/vscode-codeql
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

move config and fix tsconfig error

Browse Source
This commit is contained in:
Nora
2024-01-12 13:36:11 +00:00
parent b4a66a7690
commit 0b9e4e33b2
3 changed files with 8 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
extensions/ql-vscode/test/e2e/README.md
View File

@@ -1,17 +1,18 @@
## VS Code CodeQL E2E Tests ## VS Code CodeQL E2E Tests
When running the tests locally on a mac a different processor has to be emulated, which makes everythign VERY slow. Hence many timeouts in the test. When running the tests locally on a mac a different processor has to be emulated, which makes everythign VERY slow. Therefore we need to add higher timeouts in the test, so that they pass locally.
### How to use locally ### How to use locally
Setup Setup
- run `docker-compose build` from the e2e test folder `vscode-codeql/extensions/ql-vscode/test/e2e` - go to the e2e test folder on your terminal
- run `docker-compose up` from the e2e test folder `vscode-codeql/extensions/ql-vscode/test/e2e` - run `docker-compose build`
- run `docker-compose up`
Run tests Run tests
- run `npx playwright test --ui` from the vscode-codeql folder `vscode-codeql/extensions/ql-vscode` to follow the test while it's running. This UI has a 'locator' tool with which elements on the test screen can be - run `npx playwright test --ui` from the e2e test folder to follow the test while it's running. This UI has a 'locator' tool with which elements on the test screen can be found
- use `npx playwright test --debug` to follow the test in real time and interact with the interface, e.g. press enter or input into fields, stop and start - use `npx playwright test --debug` to follow the test in real time and interact with the interface, e.g. press enter or input into fields, stop and start
If you get failures after the first test run you can try to remove the volume data, e.g. by running `docker-compose down -v`. Sometimes already existing queries from former runs change the input the extension needs. During the test elements are created in the docker volume, e.g. the downloaded database or query data. This might interfer with other tests or when running a test twice. If that happens restart your docker volume by using `docker-compose down -v` and `docker-compose up`. Sometimes already existing queries from former runs change the input the extension needs.

2
extensions/ql-vscode/playwright.config.ts → extensions/ql-vscode/test/e2e/playwright.config.ts
View File

@@ -10,7 +10,7 @@ import { defineConfig, devices } from "@playwright/test";
* See https://playwright.dev/docs/test-configuration. * See https://playwright.dev/docs/test-configuration.
*/ */
export default defineConfig({ export default defineConfig({
testDir: "./test/e2e", testDir: ".",
timeout: 5 * 60 * 1000, timeout: 5 * 60 * 1000,
/* Run tests in files in parallel */ /* Run tests in files in parallel */

2
extensions/ql-vscode/tsconfig.json
View File

@@ -24,5 +24,5 @@
"noEmit": true "noEmit": true
}, },
"include": ["src/**/*.ts"], "include": ["src/**/*.ts"],
"exclude": ["node_modules", "test", "**/view"] "exclude": ["node_modules", "*.config.ts", "test", "**/view"]
} }