You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/contributors/ui-testing.md
+18-11Lines changed: 18 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,19 +1,22 @@
1
1
# Web Console testing
2
2
3
-
Regression UI testing is performed in the form of end-to-end integration tests using Playwright framework.
4
-
5
-
### e2e testing with Playwright
6
-
Existing Playwright tests are executed during CI
7
-
and can be run manually within provided devcontainer environment.
3
+
Regression UI testing is performed using Playwright framework.
4
+
The repository contains end-to-end (e2e) tests that are to be executed against a clean Feldera instance,
5
+
and standalone unit (ct) tests that include UI component tests and TypeScript function tests.
6
+
Existing Playwright tests are executed during CI and can be run manually within provided devcontainer environment.
7
+
Add environment variable `CI=true` when executing tests in CI setting.
8
8
9
-
### Running tests
9
+
### Running e2e tests
10
10
11
-
Run `yarn test`
12
-
to execute all tests on all supported platforms in background, or run `yarn test:ui` to open a UI to run tests interactively.
13
-
Add environment variable `CI=true` when executing tests in CI setting.
11
+
Run `yarn test-e2e` to execute all e2e tests on all supported platforms in background, or run `yarn test-e2e-ui` to open a UI to run tests interactively.
14
12
Tests should be executed against a running Pipeline Manager instance.
15
13
As an artificial limitation of scope, currently no services for Kafka, Debezium, Snowflake and other similar connector types are available for tests in the CI, so only HTTP connectors and API is available along with the UI itself.
16
14
15
+
### Running ct tests
16
+
17
+
Run `yarn test-ct` to execute all ct tests on all supported platforms in background, or run `yarn test-ct-ui` to open a UI to run tests interactively.
18
+
Unit tests do not need Feldera instance to run because they run against individual ESM modules compiled on-demand for the test.
19
+
17
20
### Contributing tests
18
21
19
22
The tests directory is `feldera/web-console/tests`.
@@ -25,15 +28,19 @@ Environment variable `PLAYWRIGHT_SNAPSHOTS_COMMIT` in `feldera/.arg` specifies t
25
28
When committing new tests or updating screenshots for existing tests, `PLAYWRIGHT_SNAPSHOTS_COMMIT` needs to be updated as well.
26
29
When testing locally, you need to manually clone `playwright-snapshots` and checkout the correct commit hash, e.g.:
0 commit comments