-
Notifications
You must be signed in to change notification settings - Fork 16
Improve nightly E2E test suite authentication issues in BrowserStack #1370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
92ca0fb to
7ad5cdf
Compare
7ad5cdf to
5a6615c
Compare
5a6615c to
d2818fe
Compare
d2818fe to
c29176d
Compare
c29176d to
fe26525
Compare
fe26525 to
2f3da8a
Compare
2f3da8a to
f401580
Compare
f401580 to
c9895e6
Compare
MelissaAutumn
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine to me, thank you!
I wonder if we can eventually figure out a wait to remove all these waits, seems like a lot of unfortunate busy work 😅.
| constructor(page: Page) { | ||
| this.page = page; | ||
| this.signInHeaderText = this.page.getByText('Enter your password'); | ||
| this.signInHeaderText = this.page.getByText('Sign in to your account'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we can just hook into the localization file for appointment and then call it by the l10n key.
...sorry just thinking ahead, no action for this PR 😄
Yes that would be ideal, but unfortunately the timing is different on local vs stage vs prod vs mobile (especially slower in BrowserStack), so it's pretty tricky. Thanks for the review! |
Fixes #1369: Restructure the nightly E2E test suite into multiple BrowserStack sessions to fix authentication issues. Also adds a check at the start of each test in case the Appointment session has timed out, then it will log in again and save the auth state before the test starts. This is still not foolproof in that the Appointment sign in session might expire during a test and then the test would fail, however in that case the very next test would sign in again.
BrowserStack links here for desktop tests and mobile tests on stage.