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: test/e2e/README.md
+14-13Lines changed: 14 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,8 +18,9 @@ npx playwright install
18
18
```
19
19
20
20
## E2E Test Prerequisites
21
-
The E2E tests require an existing Appointment (and corresponding FxA account) and associated data, and reads this from your local .env file. This includes:
22
-
- Credentials for an existing Appointment (FxA) account (email address, password)
21
+
22
+
The E2E tests require an existing TB Pro account and other settings that are read this from your local .env file. This includes:
23
+
- Credentials for an existing TB Pro account (TB Pro email and associated password)
23
24
- The account user's display name and share link:
24
25
- The display name is found in Appointment => Settings => Account => Display name.
25
26
- The share link is found in Appointment => Settings => Account => My Link.
@@ -28,7 +29,7 @@ The E2E tests require an existing Appointment (and corresponding FxA account) an
28
29
The tests expect the following Appointment application settings:
29
30
- The user scheduling availability hasn't been changed from the default settings;
30
31
- In the dashboard the default calendar view is the current month view; this is important so that the tests can find an available booking slot, etc.
31
-
- In `Booking Settings`, the `Booking Confirmation` option is enabled, so that requested appointments generate HOLD appointments that need to be confirmed
32
+
- In `Booking Settings`, the `Automatically confirm bookings if time is available` option is checked / turned on
32
33
33
34
## Running the E2E tests against your local dev environment
34
35
@@ -43,8 +44,8 @@ cp .env.dev.example .env
43
44
44
45
Then edit your local `.env` file and provide the following values:
@@ -152,13 +153,13 @@ npm run prod-sanity-test-headed
152
153
153
154
You can run the E2E tests from your local machine but against browsers provided in the BrowserStack Automate cloud.
154
155
155
-
<b>For security reasons when running the tests on BrowserStack I recommend that you use a dedicated test Appointment FxA account / credentials (NOT your own personal Appointment (FxA) credentials).</b>
156
+
<b>For security reasons when running the tests on BrowserStack I recommend that you use a dedicated test Appointment account / credentials (NOT your own personal Appointment credentials).</b>
156
157
157
-
Once you have credentials for an existing Appointemnt test account, edit your local `.env` file and add these details (more information found above):
158
+
Once you have credentials for an existing TB Pro test account, edit your local `.env` file and add these details (more information found above):
0 commit comments