✅ Add global setup for cookie acceptance in E2E tests

[sasamuku]

Add global setup for cookie acceptance in E2E tests.

Related Issue

Testing

Other Information

[changeset-bot]

⚠️ No Changeset found

Latest commit: 55a5dee

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[qodo-merge-pro-for-open-source]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Error Handling The cookie button click silently catches and ignores errors. Should validate if this is the desired behavior or if errors should be handled differently. await cookieButton.click({ timeout: 3000, force: true }).catch(() => {}) Timeout Value The hardcoded 3000ms timeout for cookie button click may need to be configurable or aligned with other timeout values in the config. await cookieButton.click({ timeout: 3000, force: true }).catch(() => {})

[qodo-merge-pro-for-open-source]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Validate element before force clicking Verify the cookie button exists before attempting to click it to prevent potential force-click issues on non-existent elements. frontend/packages/e2e/global-setup.ts [9-12] const cookieButton = page.getByRole('button', { name: 'Accept All Cookies', }) -await cookieButton.click({ timeout: 3000, force: true }).catch(() => {}) +if (await cookieButton.isVisible()) + await cookieButton.click({ timeout: 3000 }).catch(() => {}) Apply this suggestion Suggestion importance[1-10]: 8 __ Why: Checking element visibility before clicking and removing force:true is a more robust approach that prevents potential flaky tests and better handles cases when the cookie button is not present.	Medium
General	Add error handling for setup failures Add error handling and logging for the cookie button click failure. The current .catch(() => {}) silently ignores failures which could mask setup issues. frontend/packages/e2e/global-setup.ts [12] -await cookieButton.click({ timeout: 3000, force: true }).catch(() => {}) +await cookieButton.click({ timeout: 3000, force: true }).catch((error) => { + console.warn('Cookie acceptance button not found or not clickable:', error.message); +}) Apply this suggestion Suggestion importance[1-10]: 7 __ Why: Adding proper error logging for cookie button click failures would help debug test setup issues instead of silently ignoring them. This is important for test maintainability and troubleshooting.	Medium

[MH4GF]

LGTM 👍🏻