-
Notifications
You must be signed in to change notification settings - Fork 0
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
Care 767 create automation tests for menu button on mobile #44
Care 767 create automation tests for menu button on mobile #44
Conversation
1. Added Test scripts to validate Menu button that replaces navigation Bar in the Mobile devices 2. Updated the Playwright config(both) to specifically run tests on a mobile viewport for Android devices. 3. Cleaned up the code by separating the repeatable shared functionalities, such as the 'You need help now' section, the website name, and the navigation bar.
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 good to me
async verifyShareButtonsVisibility() { | ||
await Promise.all([ | ||
expect(this.shareButtonsContainer).toBeVisible(), | ||
expect(this.facebookShareButton).toBeVisible(), |
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.
As these are configurable, did we want to only expect the shareButtonsContainer, and leave the others?
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 have removed all the social buttons validations, I have kept the print icon as you mentioned that this should always be there
Added More tests to validate Share buttons and Metadata section