Docs: Missing Landings - e2e tests (#2025)

Author: urbiz-grafana

docusaurus/docs/e2e-test-a-plugin/get-started.md

@@ -1,7 +1,7 @@
 ---
 id: get-started
-title: Get started
-description: Get started
+title: Get started 
+description: Get started with plugin end-to-end testing.
 keywords:
   - grafana
   - plugins

docusaurus/docs/e2e-test-a-plugin/index.md

@@ -0,0 +1,31 @@
+---
+id: e2e-test-a-plugin
+title: Test your plugins end-to-end
+description: How to perform end-to-end tests for Grafana plugins.
+keywords:
+  - grafana
+  - plugins
+  - plugin
+  - test
+  - e2e
+  - end-to-end
+---
+
+You can test your plugins using [`@grafana/plugin-e2e`](https://www.npmjs.com/package/@grafana/plugin-e2e?activeTab=readme), a tool designed specifically for Grafana plugin developers. It extends [`@playwright/test`](https://playwright.dev/) capabilities with relevant fixtures, models, and expect matchers; enabling comprehensive end-to-end testing of Grafana plugins across multiple versions of Grafana. This package simplifies the testing process, ensuring your plugin is robust and compatible with various Grafana environments.
+
+## Why use `@grafana/plugin-e2e`?
+
+As a plugin author you want your plugins to be compatible with a range of Grafana versions. This can be challenging because things such as environment, APIs and UI components may differ from one Grafana version to another. Therefore, manually testing a plugin across multiple versions of Grafana is a tedious process, so in most cases end-to-end testing offers a better solution.
+
+The `@grafana/plugin-e2e` tool offers a consistent way to interact with the Grafana UI without having to handle UI deviations in the plugin test code. The APIs of `@grafana/plugin-e2e` are guaranteed to work with all the latest minor versions of Grafana since 8.5.0. In addition to cross-version compatibility, the tool provides a set of features that simplify the end-to-end testing experience:
+
+- **Predefined fixtures:** Offers a set of predefined fixtures that are tailored for Grafana plugin testing.
+- **Custom models:** Provides custom models that represent pages and components in Grafana, simplifying maintenance and creating reusable code to avoid repetition.
+- **Expect matchers:** Includes a range of expect matchers that are specialized for Grafana plugin assertions, helping you validate plugin behavior more effectively.
+- **Integration with Playwright:** Seamlessly integrates with the Playwright testing framework, leveraging its powerful browser automation capabilities.
+
+## End-to-end testing guides
+
+See the following guides to learn more about end-to-end testing:
+
+<DocLinkList />

docusaurus/docs/e2e-test-a-plugin/introduction.md

@@ -1,7 +1,7 @@
 ---
 id: migrate-from-grafana-e2e
 title: Migrate from @grafana/e2e
-description: How to migrate from @grafana/e2e to @grafana/plugin-e2e
+description: Migrate from @grafana/e2e to @grafana/plugin-e2e.
 keywords:
   - grafana
   - plugins

docusaurus/docs/e2e-test-a-plugin/migrate-from-grafana-e2e.md

@@ -1,7 +1,7 @@
 ---
 id: introduction
 title: How to test a data dource plugin
-description: How to test a data source plugin
+description: How to test a data source plugin.
 keywords:
   - grafana
   - plugins

docusaurus/docs/e2e-test-a-plugin/test-a-data-source-plugin/index.md

@@ -1,7 +1,7 @@
 ---
 id: test-a-panel-plugin
 title: Test a panel plugin
-description: How to test a panel plugin with @grafana/plugin-e2e
+description: How to test a panel plugin with @grafana/plugin-e2e.
 keywords:
   - grafana
   - plugins

docusaurus/docs/e2e-test-a-plugin/test-a-panel-plugin.md

@@ -1,7 +1,7 @@
 ---
 id: introduction
 title: How to test an app plugin
-description: How to test an app plugin
+description: How to test an app plugin.
 keywords:
   - grafana
   - plugins

docusaurus/docs/e2e-test-a-plugin/test-an-app-plugin/index.md

@@ -1,7 +1,7 @@
 ---
 id: api
 title: Use the API
-description: How to use the grafana/plugin-e2e API
+description: How to use the grafana/plugin-e2e API.
 keywords:
   - grafana
   - plugins

docusaurus/docs/e2e-test-a-plugin/use-the-api.md

@@ -122,5 +122,5 @@ test('should render profile', async ({ page, grafanaVersion }) => {
 
 ### Further reading
 
-- **end-to-end testing for plugins**: For comprehensive guidance on writing and running E2E tests for Grafana plugins, refer to the [documentation](../e2e-test-a-plugin/introduction.md).
+- **end-to-end testing for plugins**: For comprehensive guidance on writing and running E2E tests for Grafana plugins, refer to the [documentation](../e2e-test-a-plugin/index.md).
 - **Running end-to-end tests across multiple Grafana versions**: To learn how to configure your workflows to test plugins against different Grafana versions, see the [example workflows](../e2e-test-a-plugin/ci.md).

docusaurus/docs/how-to-guides/runtime-checks.md

@@ -170,7 +170,7 @@ The following files are crucial for your plugin's development and functionality:
   - `plugin.json`: Stores [metadata about your plugin](/reference/plugin-json), including information like its description, supported Grafana versions, and dependencies.
   - `module.ts`: The entry point for your plugin's frontend logic.
 - **Backend code** (`pkg/`): Required if your plugin has a backend component. If your plugin includes backend functionality, the code will reside in this directory, typically within `pkg/plugin/`. Backend plugins are written in Go, and `main.go` serves as the entry point for your backend logic.
-- **Test files** (`tests/`): Optional, but strongly recommended to ensure plugin quality. This folder contains your plugin’s test files, typically suffixed with `.spec.ts` for frontend tests. You can [learn more about testing your plugin](/e2e-test-a-plugin/introduction) in our E2E testing guide.
+- **Test files** (`tests/`): Optional, but strongly recommended to ensure plugin quality. This folder contains your plugin’s test files, typically suffixed with `.spec.ts` for frontend tests. You can [learn more about testing your plugin](/e2e-test-a-plugin/index.md) in our E2E testing guide.
 - **Other files**:
   - `docker-compose.yaml`: Required for Docker environment only. Contains the Docker configuration for running a local development instance of Grafana.
   - `CHANGELOG.md`: Required. Documents the history of changes and updates made to the plugin.