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: packages/tests-e2e/README.md
+9-31Lines changed: 9 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,46 +4,24 @@ This package currently contains all the end-to-end tests for testing the React p
4
4
5
5
## Running Tests Locally
6
6
7
-
This package is intended to test the local Playground React deployment connected to the staging backend deployment.
7
+
Playground is locally run within Playwright for both Complete and Connect tests. For reference look at `utils/playground.ts`.
8
8
9
-
### Setup
9
+
This means that tests can simply be run with a single command. The command depends on whether you want to run it headless or with UI.
10
10
11
-
Copy the contents of .env.example into .env.local.
12
-
For `PLAYWRIGHT_JWT_TOKEN` environment variable, request the JWT token from Martin or Stefan.
13
-
For `PLAYWRIGHT_MICROSOFT_EMAIL` and `PLAYWRIGHT_MICROSOFT_PASSWORD` environment variables, request the credentials from Anders or Martin. You can also create your own Microsoft account for testing.
14
-
15
-
Make sure that the local Playground React deployment is configured to connect to the staging frontend API endpoints in `playground/react/.env`.
0 commit comments