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

changed flakey tests for query-workbench #1025

Closed

Conversation

sumukhswamy
Copy link
Contributor

@sumukhswamy sumukhswamy commented Jan 31, 2024

Description

added changes for workbench changes

Issues Resolved

[List any issues this PR will resolve]

Check List

  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: sumukhswamy <[email protected]>
@ruanyl
Copy link
Member

ruanyl commented Jan 31, 2024

@sumukhswamy The lint check failed, could you take a look? The query workbench release tests are failed as well.

@sumukhswamy
Copy link
Contributor Author

@sumukhswamy The lint check failed, could you take a look? The query workbench release tests are failed as well.

there is PR pending to be merged in workbench which has a few changes thats why the tests are failing

Signed-off-by: sumukhswamy <[email protected]>
@SuZhou-Joe
Copy link
Member

@sumukhswamy Is the fix merged in main?

@sumukhswamy
Copy link
Contributor Author

@sumukhswamy Is the fix merged in main?

yes it has

@SuZhou-Joe
Copy link
Member

SuZhou-Joe commented Feb 8, 2024

@sumukhswamy could you please post the result in your local env as the latest 3.0.0 build has some error when launching.

cy.wait(QUERY_WORKBENCH_DELAY);
cy.get('.euiButton__text[title=PPL]').click({ force: true });
cy.wait(QUERY_WORKBENCH_DELAY);
cy.wait(1000);
Copy link
Member

Choose a reason for hiding this comment

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

Any reason why we replace the const QUERY_WORKBENCH_DELAY with 1000?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants