Skip to content
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

feat(RHINENG-8253): Update risk label in cluster page #706

Merged
merged 1 commit into from
Mar 21, 2024

Conversation

AsToNlele
Copy link
Contributor

@AsToNlele AsToNlele commented Mar 13, 2024

@AsToNlele AsToNlele requested a review from a team as a code owner March 13, 2024 15:09
@gkarat gkarat added the enhancement New feature or request label Mar 14, 2024
@AsToNlele
Copy link
Contributor Author

/retest

@AsToNlele
Copy link
Contributor Author

I've restarted like a million times all is working...

@AsToNlele AsToNlele force-pushed the RHINENG-8253 branch 2 times, most recently from 7dc087f to 7250657 Compare March 20, 2024 14:30
@@ -89,6 +89,8 @@ function checkFiltering(
checkTableHeaders(tableHeaders);
} else {
cy.get('[data-ouia-component-id=loading-skeleton]').should('not.exist');
// eslint-disable cypress/no-unnecessary-waiting
cy.wait(1000);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is a very good example of where we actually don't need unnecessary waiting :-)

Can we think of why our tests are timing out or not able to find the expected data under the columns? Is it the fact that the table is still in the loading state? If so, what should appear if we consider the table loaded? Instead of waiting generic 1 second, can we just wait for some of the first row data to appear?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I wanted to give it a try if it eventually helps something, looks like it doesn't

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Loading state I've fixed few lines below by adding this
cy.get('[data-ouia-component-id=loading-skeleton]').should('not.exist');
Waits until the skeleton is gone

@@ -18,4 +18,5 @@ module.exports = defineConfig({
return config;
},
},
retries: 2,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see this was introduced earlier already on master. But I believe this is a general anti-pattern when dealing with flaky tests. I strongly discourage from using any retries since we will have even less insights into why our tests or our UI is flaky.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the end this usually didn't help with anything, if it failed once then it failed in the retries as well. But I agree it shouldn't be there

@gkarat gkarat merged commit 3f21e6e into RedHatInsights:master Mar 21, 2024
0 of 2 checks passed
@gkarat
Copy link
Collaborator

gkarat commented Mar 27, 2024

🎉 This PR is included in version 1.42.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants