grafana/e2e-playwright/test-plugins
Torkel Ödegaard 28c19036f1
ButtonSelect: Fixes menu shadow (fixes issue with RefreshPicker) (#111431)
* ButtonSelect: Fixes menu shadow

* Update e2e tests to look in portal
2025-09-22 19:55:27 +02:00
..
frontend-sandbox-app-test E2E: migrate to playwright (#107241) 2025-07-11 10:31:33 +01:00
frontend-sandbox-datasource-test E2E: migrate to playwright (#107241) 2025-07-11 10:31:33 +01:00
frontend-sandbox-panel-test E2E: migrate to playwright (#107241) 2025-07-11 10:31:33 +01:00
grafana-extensionstest-app ButtonSelect: Fixes menu shadow (fixes issue with RefreshPicker) (#111431) 2025-09-22 19:55:27 +02:00
grafana-test-datasource Release: Bump version to 12.3.0-pre (#110974) 2025-09-12 17:54:11 +00:00
README.md E2E: migrate to playwright (#107241) 2025-07-11 10:31:33 +01:00

README.md

Test plugins

The e2e test server automatically scans and looks for plugins in this directory.

To add a new test plugin:

  1. If provisioning is required you may update the YAML config file in /devenv.
  2. Add the plugin ID to the allow_loading_unsigned_plugins setting in the test server's configuration file.

Building a test plugin with webpack

If you wish to build a test plugin with webpack, you may take a look at how the grafana-extensionstest-app is wired. A few things to keep in mind:

  • the package name needs to be prefixed with @test-plugins/
  • extend the webpack config from @grafana/plugin-configs and use custom webpack config to only copy the necessary files (see example here)
  • keep dependency versions in sync with what's in core

Local development

1: Install frontend dependencies: yarn install --immutable

2: Build and watch the core frontend yarn start

3: Build and watch the test plugins yarn e2e:plugin:build:dev

4: Build the backend make build-go

5: Start the Grafana e2e test server with the provisioned test plugin PORT=3000 ./scripts/grafana-server/start-server