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

[SIEM] Fixes 'sets and reads the url state for timeline by id' timeline Cypress test #75125

Merged
merged 8 commits into from
Aug 24, 2020

Conversation

MadameSheema
Copy link
Member

@MadameSheema MadameSheema commented Aug 16, 2020

Summary

In this PR we are fixing the 'sets and reads the url state for timeline by id' timeline Cypress test.

Before we were getting the timeline id from the url before creating it. That was not completely reliable and made also the test slow. Now we are getting the timeline id from the API call, making the test faster and reliable.

@MadameSheema
Copy link
Member Author

@elasticmachine merge upstream

@MadameSheema
Copy link
Member Author

@elasticmachine merge upstream

@MadameSheema MadameSheema self-assigned this Aug 17, 2020
@MadameSheema MadameSheema added release_note:skip Skip the PR/issue when compiling release notes Team:SIEM v7.10.0 v8.0.0 labels Aug 17, 2020
@MadameSheema MadameSheema marked this pull request as ready for review August 17, 2020 13:36
@MadameSheema MadameSheema requested review from a team as code owners August 17, 2020 13:36
@elasticmachine
Copy link
Contributor

Pinging @elastic/siem (Team:SIEM)

@MadameSheema
Copy link
Member Author

@elasticmachine merge upstream

@andrew-goldstein
Copy link
Contributor

@elasticmachine merge upstream

@andrew-goldstein
Copy link
Contributor

When I focused url_state.spec.ts and ran node x-pack/plugins/security_solution/scripts/loop_cypress_tests.js 10, it failed 1 out of 10 times with the following error:

assertion-error

Cypress captured the following screenshot when the test failed:

url state -- sets and reads the url state for timeline by id (failed)

Copy link
Contributor

@andrew-goldstein andrew-goldstein left a comment

Choose a reason for hiding this comment

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

Thanks for updating this test @MadameSheema!
Tested locally by focusing url_state.spec.ts and running node x-pack/plugins/security_solution/scripts/loop_cypress_tests.js 10 to test for flakes
LGTM 🚀

@andrew-goldstein
Copy link
Contributor

@elasticmachine merge upstream

@MadameSheema
Copy link
Member Author

@elasticmachine merge upstream

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Build metrics

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@MadameSheema MadameSheema merged commit 3768aab into elastic:master Aug 24, 2020
@MadameSheema MadameSheema deleted the fixes-url-timeline-test branch August 24, 2020 12:41
MadameSheema added a commit to MadameSheema/kibana that referenced this pull request Aug 24, 2020
…ne Cypress test (elastic#75125)

* fixes 'sets and reads the url state for timeline by id' timeline ttest

* makes test more reliable

Co-authored-by: Elastic Machine <[email protected]>
MadameSheema added a commit that referenced this pull request Aug 24, 2020
…ne Cypress test (#75125) (#75745)

* fixes 'sets and reads the url state for timeline by id' timeline ttest

* makes test more reliable

Co-authored-by: Elastic Machine <[email protected]>

Co-authored-by: Elastic Machine <[email protected]>
@MindyRS MindyRS added the Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. label Sep 23, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_note:skip Skip the PR/issue when compiling release notes Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM v7.10.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants