-
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
Initial unit tests for embedded_visualize_handler #31324
Initial unit tests for embedded_visualize_handler #31324
Conversation
Pinging @elastic/kibana-app |
This comment has been minimized.
This comment has been minimized.
💚 Build Succeeded |
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.
LGTM
Reverts #31324, failing on master
This PR started causing master to fail, so I reverted it in #32615 |
…2615) Reverts elastic#31324, failing on master
This was my bad, the last green CI build was awhile ago, and I should've re-run it as a precautionary measure. Opened #32657 with the same PR rebased on master. Will merge & backport that one instead once a green build comes back. |
Fixes #30422
This is a first pass at unit tests for the
embedded_visualize_handler
. For now I prioritized public methods & interfaces, and have also tried to cover some of the issues we've seen come up recently with the work on the new pipeline (e.g. #30405, #30830) -- but I'm open to suggestion on any other pieces we feel are particularly error-prone that would be worth spending time on now.Public stuff that hasn't been tested yet is focused around rendering, because that's where the two paths diverge (pipeline/visualize data loaders). Also for the legacy
visualizationLoader
, it is very tricky to get things working as you have to try mocking theVis
object, especially without the help of the usualngMock.module
andngMock.inject
setup.Since we are looking to move toward the expression pipeline as soon as things are stable, I hesitate to invest the time in getting tests working with
visualizationLoader
-- I think that time is better spent focusing on tests for the pipeline/interpreter.Ran this suite both with and without the pipeline; everything should pass in both cases.