Chore: Update to latest e2e-selectors

[ashharrison90]

What this PR does / why we need it:

• updates to the latest e2e-selectors
• disables the splash screen
• fixes a couple of methods to work with the new selectors
• disables dashboardNewLayouts
  • this needs fixing, but i'm not the person to do it 😅

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

📦 Published PR as canary version: Canary Versions

✨ Test out this PR locally via:

npm install @grafana/plugin-e2e@3.4.13-canary.2569.24237094857.0
# or 
yarn add @grafana/plugin-e2e@3.4.13-canary.2569.24237094857.0

[github-actions]

Hello! 👋 This repository uses Auto for releasing packages using PR labels.

✨ This PR can be merged and will trigger a new patch release.
NOTE: When merging a PR with the release label please avoid merging another PR. For further information see here.

[Copilot]

Pull request overview

Updates the @grafana/plugin-e2e test harness to align with the latest @grafana/e2e-selectors, adjusting affected selectors/usages and tweaking the local Grafana docker setup to keep the e2e suite stable.

Changes:

• Bump @grafana/e2e-selectors to a newer build.
• Update a panel edit test and alert rule page object to use updated selector/label behavior.
• Disable Grafana splashScreen and dashboardNewLayouts feature toggles in the plugin-e2e docker compose environment.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
packages/plugin-e2e/tests/as-admin-user/panel/panelEdit.spec.ts	Updates a color picker option label to match new selector/label expectations.
packages/plugin-e2e/src/models/pages/AlertRuleEditPage.ts	Switches default query row lookup to use Grafana selectors instead of a hard-coded test id.
packages/plugin-e2e/package.json	Bumps @grafana/e2e-selectors dependency version.
packages/plugin-e2e/docker-compose.yaml	Disables splash screen and new dashboard layouts to reduce e2e friction.

[Copilot]

@grafana/e2e-selectors was bumped here, but the repo-level package-lock.json still pins the previous version. This will cause CI installs to keep using the old selectors unless the lockfile is updated (run npm install / update the lockfile).

[Copilot]

In the advanced-mode-disabled branch, QueryEditorRows.rows is passed directly as the query root. Since this selector represents a collection of rows (used elsewhere with .filter()/.last()), this can unintentionally target multiple rows and later actions may fail Playwright strictness or operate on the wrong row. Narrow the locator to a single row (e.g. .first()), or otherwise uniquely identify the default row.

Suggested change

	this.getByGrafanaSelector(this.ctx.selectors.components.QueryEditorRows.rows)
	this.getByGrafanaSelector(this.ctx.selectors.components.QueryEditorRows.rows).first()

[github-actions]

Playwright test results

Image Name	Version	Result	Report
grafana-dev	13.1.0-24236083202	✅
grafana-enterprise	12.4.2	✅
grafana-enterprise	12.0.10	✅
grafana-enterprise	10.4.19	✅
grafana-enterprise	9.3.16	✅
grafana-enterprise	8.5.27	✅

Troubleshooting

404 when clicking on View report

By default, the deploy-report-pages Action deploys reports to the gh-pages branch. However, you need to take an extra step to ensure that GitHub Pages can build and serve the site from this branch. To do so:

1. Go to the Settings tab of your repository.
2. In the left-hand sidebar, click on Pages.
3. Under Source, select Deploy from a branch, then choose the gh-pages branch.

This action needs to be completed manually in order for your GitHub Pages site to be built and accessible from the gh-pages branch. Once configured, GitHub will automatically build and serve the site whenever new reports are deployed.

[sunker]

Thanks a lot for raising this @ashharrison90!

I created an issue for adding support for new dashboard layout and splash screen in plugin e2e. Will look into this asap.

[grafana-plugins-platform-bot]

🚀 PR was released in @grafana/plugin-e2e@3.4.13 🚀