dependabot[bot]andsamsch
235dec4e77
* Bump glob in /e2e-playwright/test-plugins/grafana-extensionstest-app Bumps [glob](https://github.com/isaacs/node-glob) from 10.4.1 to 11.1.0. - [Changelog](https://github.com/isaacs/node-glob/blob/main/changelog.md) - [Commits](https://github.com/isaacs/node-glob/compare/v10.4.1...v11.1.0) --- updated-dependencies: - dependency-name: glob dependency-version: 11.1.0 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com> * update lockfile --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: samsch <git@samsch.org>
Test plugins
The e2e test server automatically scans and looks for plugins in this directory.
To add a new test plugin:
- If provisioning is required you may update the YAML config file in
/devenv. - Add the plugin ID to the
allow_loading_unsigned_pluginssetting 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-configsand 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