Docs: Plugin E2E - Panel plugin docs #852
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
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. |
sunker
requested review from
oshirohugo,
sympatheticmoose,
josmperez and
mckn
and removed request for
a team
josmperez
reviewed
Apr 8, 2024
There was a problem hiding this comment.
I have edited this document in https://github.com/grafana/plugin-tools/pull/852/commits. Please take a look and ensure that no errors have been introduced.
Looks good, thanks Joe! |
Ukochka
pushed a commit
that referenced
this pull request
Apr 16, 2024
Co-authored-by: Joe Perez <joseph.perez@grafana.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
This PR adds a guide on how to e2e test panel plugins. Feedback on parts that are missing are very much welcome!
I feel like we should say something about the complexity that comes with testing visual components such as lines and curves, and why we discourage screenshot testing. At the same time, I want plugin authors to be free to chose whatever path they think is right. WDYT?
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer: