mirror of
https://github.com/grafana/grafana.git
synced 2025-02-25 18:55:37 -06:00
* build test apps with webpack * add extensions test app * update e2e tests * remove non-build test apps using amd * use @grafana/plugin-configs rather than create-plugin config * Update e2e/plugin-e2e/plugin-e2e-api-tests/as-admin-user/extensions/usePluginComponents.spec.ts Co-authored-by: Jack Westbrook <jack.westbrook@gmail.com> * Update package.json Co-authored-by: Jack Westbrook <jack.westbrook@gmail.com> * use run dir variable instead of hardcoded path * add dummy licence file * add separate step for building test plugins * support nested plugins * remove react-router-dom from the externals array * remove add_mode dev * lint starlark * pass license path as env variable * fix the path * chore(e2e-plugins): clean up dependencies to match core versions * refactor(e2e-plugins): prefer extending webpack plugins-config * docs(e2e-plugins): add basic info to extensions test plugin readme * update readme * change dir name from custom plugins to test plugins * change root readme * update lockfile --------- Co-authored-by: Jack Westbrook <jack.westbrook@gmail.com> |
||
---|---|---|
.. | ||
as-admin-user | ||
as-viewer-user | ||
mocks | ||
errors.ts | ||
README.md |
@grafana/plugin-e2e API tests
The purpose of the E2E tests in this directory is not to test the plugins per se - it's to verify that the fixtures, models and expect matchers provided by the @grafana/plugin-e2e
package are compatible with the latest version of Grafana. If you find that any of these tests are failing, it's probably due to one of the following reasons:
- you have changed a value of a selector defined in @grafana/e2e-selector
- you have made structural changes to the UI
For information on how to address this, follow the instructions in the contributing guidelines for the @grafana/plugin-e2e package in the plugin-tools repository.