-
Notifications
You must be signed in to change notification settings - Fork 40
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
[RFR] Update open() for a few classes #1217
Changes from 5 commits
3c78d62
71ef540
c4ebaee
2416513
3619ba3
4463b9d
6a39766
cfe9225
869eb46
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1373,8 +1373,8 @@ export function goToPage(page: number): void { | |
} | ||
|
||
export function selectUserPerspective(userType: string): void { | ||
cy.get(commonView.optionMenu).click(); | ||
cy.get(commonView.actionMenuItem).contains(userType).click(); | ||
cy.get("button.pf-v5-c-menu-toggle.pf-m-full-width").click({ force: true }); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. if the selector has changed ,let's make the change in the commonView.optionmenu. This change will have to be tested for few more tests . There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hi @sshveta , The selector hasn't changed . I'm using a different locator to get the job done because with the current locator, there are intermittent issues and the user perspective toggle doesn't always get clicked. Sure, I could run the PR on additional tests . There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This PR tests the following -
|
||
cy.get(commonView.actionMenuItem).contains(userType).click({ force: true }); | ||
} | ||
|
||
export function selectWithinModal(selector: string): void { | ||
|
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 think a timeout of 100 secods is too much.
I think if a page takes more than 35 secs (the current timeout we have for other tests) to load the test should fail because something is wrong there
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.
Yes, 100 seconds is too long for a page to load. I have reported a bug for that .
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.
we need to reduce the time and let this test fail .
It will impact overall time of execution.
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.
Lot of tests are using application page , let's reduce it to 5 Sec