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

[Security Solution] Re-enable the timelines url state test #173536

Merged
merged 5 commits into from
Dec 20, 2023

Conversation

lgestc
Copy link
Contributor

@lgestc lgestc commented Dec 18, 2023

@lgestc lgestc changed the title [Security Solution] Re-enable the flaky test, and enable just that case [Security Solution] Re-enable the timelines url state test Dec 18, 2023
@lgestc lgestc force-pushed the iss_172503_url_state_flaky_test branch from dd3cb9c to c898971 Compare December 19, 2023 14:38
@lgestc
Copy link
Contributor Author

lgestc commented Dec 19, 2023

/ci

@lgestc lgestc added Team:Threat Hunting:Investigations Security Solution Investigations Team backport:skip This commit does not require backporting release_note:skip Skip the PR/issue when compiling release notes labels Dec 19, 2023
@lgestc lgestc marked this pull request as ready for review December 19, 2023 16:03
@lgestc lgestc requested a review from a team as a code owner December 19, 2023 16:03
@lgestc lgestc enabled auto-merge (squash) December 19, 2023 16:48
Copy link
Contributor

Choose a reason for hiding this comment

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

We should get rid of the before and use beforeEach only. If a test fails then all the code in the before will not be run again when the test is retried.
Also why login twice (currently we call login in the before then again in the beforeEach).

Once you move the content of the before into the beforeEach, I wonder if we should clear all created timeline to make sure that the tests start fresh always? (here is the function that does it for you).

Also I feel like the nested describe (line 45) isn't doing anything, so let's remove it!

@lgestc lgestc force-pushed the iss_172503_url_state_flaky_test branch 2 times, most recently from f6eb950 to 43b7986 Compare December 20, 2023 14:08
Copy link
Contributor

@PhilippeOberti PhilippeOberti left a comment

Choose a reason for hiding this comment

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

I took the liberty of adding deleteTimelines(); to the beforeEach just to make sure we're starting each test with a correct state.

I tested locally by running each test a bunch of files and we're good!
Thanks for making all the changes!

@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:Threat Hunting:Investigations Security Solution Investigations Team v8.13.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants