-
Notifications
You must be signed in to change notification settings - Fork 32
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
Plugin E2E: Enable testing the variable editor #553
Conversation
Hello! 👋 This repository uses Auto for releasing packages using PR labels. ✨ This PR can be merged. It will not be considered when calculating future versions of the npm packages and will not appear in the changelogs. |
349427d
to
481446e
Compare
e3dfea5
to
6e38d96
Compare
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! 🚀
packages/plugin-e2e/src/api.ts
Outdated
* | ||
* Use {@link PanelEditPage.setVisualization} to change the visualization | ||
* Use {@link PanelEditPage.datasource.set} to change the datasource | ||
* Use {@link PanelEditPage.datasource.set} to change the |
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.
nit: should this change should be reverted?
What this PR does / why we need it:
This PR adds fixtures, models and expect matchers that enable testing a custom variable query editor and the variable query runner in a data source plugin.
Please not that the playwright tests under
packages/plugin-e2e/tests
are not actually part of the plugin-e2e package. They are there to test the features that are exposed by the package. They can also function as a spec of how the package can be used. We may want to move them to plugin-examples eventually.Which issue(s) this PR fixes:
Part of #576
Fixes #
Special notes for your reviewer: