Docs: Instructions on how to write E2E tests for app plugins #891
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. |
mckn
added
minor
mckn
requested review from
Ukochka,
sunker and
josmperez
and removed request for
a team
There was a problem hiding this comment.
Hi @mckn - Please take a look at my suggestions in my recent commits related to doc style, clarity, and so on. Many of these are related to doc style preference for simple indicative tense and avoidance of gerunds. Let me know if you have any questions.
Love it! There is only one thing that I would like to change. I'm adding a comment with your name to it so we can discuss it in this PR. Hope that is ok 🙏🏻 |
docusaurus/docs/e2e-test-a-plugin/test-an-app-plugin/app-pages.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Marcus Andersson <marcus.andersson@grafana.com>
What this PR does / why we need it:
This PR provides some instructions on how to structure your E2E tests for app plugins. Hopefully it show case two different patterns for improving readability and to make it easier to share logic between tests.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
This is a rough draft so feel free to provide bigger text changes that would make it easier to understand the documentation.