-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Make panel action tests more generic #22174
Conversation
💔 Build Failed |
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 pending passing tests (code review only). Thanks for following through on this, great to have it generalized.
💔 Build Failed |
💔 Build Failed |
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.
I'd love to add a plugin to this that is generated by the plugin generator, and then treat that as a "snapshot" test for the plugin generator, making sure that is matches the generated output that is committed to the repo, and requiring that we update the snapshot and possible any tests whenever we update the plugin generator.
Code LGTM, relying on CI to verify it works.
💚 Build Succeeded |
* Make panel action tests more generic * Remove test file * Add simple app tests * Shorten/fix import * Remove unneeded task * Add debug output * Allow duplicate --plugin-path params * Remove debugging options * Add README
This PR makes the panel action tests more generic and giving the option of having plugin tests in general.
It also fixes the issue, that these weren't executed at all on CI and thus already were broken since #19261 when
env
was removed.@spalger this test suite might qualify later for pulling it into it's separate Jenkins job, right now it adds around 5 minutes to our build time☹️