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: dev-packages/e2e-tests/README.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,8 +57,14 @@ EOF
57
57
58
58
Make sure to add a `test:build` and `test:assert` command to the new app's `package.json` file.
59
59
60
-
Add the new test app to `test-application` matrix in `.github/workflows/build.yml` for the `job_e2e_tests` job. If you
61
-
want to run a canary test, add it to the `canary.yml` workflow.
60
+
Test apps in the folder `test-applications` will be automatically picked up by CI in the job `job_e2e_tests` (in `.github/workflows/build.yml`).
61
+
The test matrix for CI is generated in `dev-packages/e2e-tests/lib/getTestMatrix.ts`.
62
+
63
+
For each test app, CI checks its dependencies (and devDependencies) to see if any of them have changed in the current PR (based on nx affected projects).
64
+
For example, if something is changed in the browser package, only E2E test apps that depend on browser will run, while others will be skipped.
65
+
66
+
You can add additional information about the test (e.g. canary versions, optional in CI) by adding `sentryTest` in the `package.json`
67
+
of a test application.
62
68
63
69
**An important thing to note:** In the context of the build/test commands the fake test registry is available at
64
70
`http://127.0.0.1:4873`. It hosts all of our packages as if they were to be published with the state of the current
0 commit comments