-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Infra UI] Processes tab test change: Wait for page loading #165303
[Infra UI] Processes tab test change: Wait for page loading #165303
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI) |
💚 Build Succeeded
Metrics [docs]
To update your PR or re-run it, just comment with: |
@@ -233,6 +233,7 @@ export default ({ getPageObjects, getService }: FtrProviderContext) => { | |||
describe('Processes Tab', () => { | |||
before(async () => { | |||
await pageObjects.assetDetails.clickProcessesTab(); | |||
await pageObjects.header.waitUntilLoadingHasFinished(); |
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.
Do you think we need to add the same thing for other tabs as well?
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 have it when initially loading the page - in theory, repeating this is not needed for most cases there is also a timeout so it shouldn't reach it. Here we are checking the content of an element that is still not available which results in having an empty string as value - I guess because we use getVisibleText
( the other tabs we check the elements directly and here we try to get the content of an element which is still not loaded)
I am not against having this in the other tabs but I don't see any failed tests in the other scenarios, maybe I am missing something or it's not an issue 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.
Ah, got it, good point about getVisibleText
, that's probably the difference with other tabs and we don't need to add wait for them 🙌
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.
🚀
Closes #160796 ## Summary As we see in the picture from the failed build we are trying to check the values when there are still spinners on the screen (so the data is still loading). <img width="1791" alt="image" src="https://github.com/elastic/kibana/assets/14139027/94608e6b-21b1-4435-9cee-efbf5a57f4ac"> To fix that I am now waiting for the page to load. This PR will be backported to fix the issue in 8.9 and I will add a follow-up PR (#165303) for the same fix in node details tests. [Build](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/3035)
Related to #160796
Summary
This PR adds the change explained here in the new node details page tests.