-
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
Refactor toast message by test subj #176889
Refactor toast message by test subj #176889
Conversation
/ci |
Flaky x50 for x-pack/test/cloud_security_posture_functional/config.ts: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5173 |
@elasticmachine merge upstream |
packages/kbn-ftr-common-functional-ui-services/services/toasts.ts
Outdated
Show resolved
Hide resolved
…mour/kibana into refactor-toastMessageByTestSubj
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.
Thanks, the new changes make a lot of sense to me
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.
Code LGTM
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
History
To update your PR or re-run it, just comment with: |
## Summary Refactor `toastMessageByTestSubj` method to two methods, instead of being nested. ## Why We feel that the this method is not ergonomic to our purposes. So, let's simplify it so that our devs can make use of it, easily. This is apart of myriad efforts to clean things up and centralize. Lastly, it's a follow up pr to [[FTR] Refactor toasts svc ](elastic#174222) Note: The flaky runner was [run against the only config that uses these two additional methods, successfully](elastic#176889 (comment)). Resolves elastic#176570 --------- Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Dzmitry Lemechko <[email protected]>
Summary
Refactor
toastMessageByTestSubj
method to two methods, instead of being nested.Why
We feel that the this method is not ergonomic to our purposes.
So, let's simplify it so that our devs can make use of it, easily.
This is apart of myriad efforts to clean things up and centralize.
Lastly, it's a follow up pr to [FTR] Refactor toasts svc
Note: The flaky runner was run against the only config that uses these two additional methods, successfully.
Resolves #176570