[BUG] Fix strict mode violation in notification search test #3307

Bug Description

The test "notification search filters and highlights correctly" attempts to locate and click the notification bell button using page.getByRole("button", { name: /Notifications/ }). However, in responsive dashboard layouts, there are often multiple elements matching this locator in the DOM (e.g., one in the desktop navigation and one in the mobile navigation menu). This causes a Playwright strict mode violation (Error: strict mode violation: locator resolved to multiple elements).

The first test correctly mitigates this by chaining .first() to the locator, but the second test misses this, leading to flakiness or outright failure during execution.

Steps to Reproduce

Run the Playwright test suite against the dashboard.

The first test ("notification bell opens and closes drawer") passes because it specifically targets .first() to select the matched bell button.

The second test ("notification search filters and highlights correctly") attempts to click the button without .first().

Playwright throws a strict mode violation error because it finds multiple "Notifications" buttons in the DOM and doesn't know which one to click.

Affected Area

Other

Screenshots

No response

Browser & OS

No response

Environment

None

Additional Context

No response