mirror of https://github.com/grafana/grafana.git
f074431a36
* Plugins: add card extension to nav-landing-page * feat(nav-landing-page): update card extension to include category and onClick support * feat(NavLandingPage): add setPluginLinksHook to test setup * feat(NavLandingPageCard): refactor className handling using cx for better style management * feat(NavLandingPage): update card extension targets to use plural form for consistency * feat(NavLandingPage): add warning for mutually exclusive extension points |
||
|---|---|---|
| .. | ||
| frontend-sandbox-app-test | ||
| frontend-sandbox-datasource-test | ||
| frontend-sandbox-panel-test | ||
| grafana-extensionstest-app | ||
| grafana-test-datasource | ||
| README.md | ||
README.md
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