-
Notifications
You must be signed in to change notification settings - Fork 269
test(amazonQ): Q Dev Profile UI tests #5979
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
base: main
Are you sure you want to change the base?
Conversation
Still need to update CI to use new test users |
const pages = await browser.pages() | ||
|
||
// Use the last page (most recently active) | ||
const activePage = pages[pages.length - 1] |
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 not found a good way to do this. This is flaky, but iterating through all the pages like the other tests also doesn't work and results in false positives/negatives for what is actually displayed. I have not found a way to get the active browser page from headless puppeteer.
} | ||
|
||
@Test | ||
fun `Test single dev profile user accounts`() { |
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.
Left out @ssologin until CI is configured. Both users are on the same IDC url. How can we select which user each test will use on CI?
Qodana Community for JVM1 new problem were found
💡 Qodana analysis was run in the pull request mode: only the changed files were checked Contact Qodana teamContact us at [email protected]
|
e2e tests for Q dev profile behavior
Types of changes
Description
Checklist
License
I confirm that my contribution is made under the terms of the Apache 2.0 license.