Fixes #31636: wait for popover name to resolve in avatar navigation test

[harsh-vador]

Describe your changes:

Fixes #31636

Users.spec.ts › User Profile Feed Interactions › Should navigate to user profile from feed card avatar click fails intermittently on the merge queue with:

Error: expect(locator).toHaveText(expected) failed
Locator:  locator('[data-testid="user-display-name"]')
Expected: ""
Received: "<user display name>"

Root cause. PopoverTitle (src/components/common/PopOverCard/PopoverTitle.component.tsx) resolves the popover user via useEntityPopoverData. Until that request resolves, userData is undefined, so displayName is '' and [data-testid="user-name"] renders empty. The test captured the expected name with textContent() immediately after the popover became visible — and the popover becomes visible before its user request resolves. On a slow run it captured '' and then asserted the profile-page title equals '', while the page correctly showed the real display name.

Fix. Wait for the popover name to resolve before capturing it, so the assertion compares two real display names:

const userNameElement = popover.getByTestId('user-name');

await expect(userNameElement).not.toBeEmpty();

const expectedUserName = await userNameElement.textContent();

Test-only change; no product code touched.

Type of change:

• Bug fix

High-level design:

N/A — small change.

Tests:

Use cases covered

• Hovering a feed card avatar and clicking the user name in the popover navigates to that user's profile page, and the profile title matches the name shown in the popover.

Unit tests

Not applicable — no product logic changed.

Backend integration tests

Not applicable (no backend API changes).

Ingestion integration tests

Not applicable (no ingestion changes).

Playwright (UI) tests

• Updated: openmetadata-ui/src/main/resources/ui/playwright/e2e/Pages/Users.spec.ts

Manual testing performed

1. yarn lint:playwright — 0 errors (only pre-existing no-force-option / no-wait-for-selector warnings on untouched lines).

UI screen recording / screenshots:

Not applicable — no UI changes.

Checklist:

• I have read the CONTRIBUTING document.
• My PR title is Fixes <issue-number>: <short explanation>
• My PR is linked to a GitHub issue via Fixes #<issue-number> above.
• I have commented on my code, particularly in hard-to-understand areas.
• For UI changes: not applicable, no UI changes.
• I have added tests (unit / integration / Playwright as applicable) and listed them above.
• I have added a test that covers the exact scenario we are fixing (the flaky test itself is the covered scenario).

🤖 Generated with Claude Code

Greptile Summary

The PR stabilizes the user-profile avatar navigation test by waiting for the asynchronously loaded popover name before capturing it.

• Adds a web-first assertion that waits for the popover username to become non-empty.
• Retains the existing navigation and profile-name comparison flow.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
openmetadata-ui/src/main/resources/ui/playwright/e2e/Pages/Users.spec.ts	Adds appropriate synchronization before reading the asynchronously resolved popover username; no blocking issue was identified.

_{Reviews (2): Last reviewed commit: "Merge branch 'main' into fix/flaky-user-..." | Re-trigger Greptile}

[github-actions]

❌ PR checklist incomplete

This PR cannot be merged until the following are addressed on its linked issue:

• Linked issue Flaky Playwright test: user profile avatar navigation captures empty expected name #31636 is not added to the Shipping project.

The fields live on the linked issue in the Shipping project (open the issue → right sidebar → Projects). After you set them, re-run this check (or push a commit) — issue/project changes do not re-trigger it automatically.

Maintainers can bypass this check by adding the skip-pr-checks label.

[github-actions]

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

[github-actions]

✅ Playwright Results — workflow succeeded

Validated commit ed2fcaf82a2a14ca11acc94207d82bcbf45379e6 in Playwright run 32056826158, attempt 1.

✅ 75 passed · ❌ 0 failed · 🟡 0 flaky · ⏭️ 0 skipped · 🧰 0 lifecycle flaky

Performance

Blocking targets: ✅ met · Optimization targets: 🟡 in progress

Shard-job maxima below are not the full workflow wall time; the linked run includes build, fixture, planning, and reporting.

🕒 Full workflow signal wall (to summary) 48m 50s

⏱️ Max setup 1m 36s · max shard execution 7m 30s · max shard-job elapsed before upload 13m 28s · reporting 2s

🌐 162.21 requests/attempt · 1.71 app boots/UI scenario · 0.00% common-shard skew

Optimization targets still in progress:

• Application boot ratio was 1.71 per UI scenario (137 boots / 80 scenarios; convergence target: at most 1).

Shard	Passed	Failed	Flaky	Skipped	Lifecycle failed	Lifecycle flaky
✅ Shard chromium-01	75	0	0	0	0	0

📦 Download artifacts

How to debug locally

# Download playwright-test-results-<shard> artifact and unzip
npx playwright show-trace path/to/trace.zip    # view trace

[github-actions]

Changes have been cherry-picked to the 2.0 branch.

[gitar-bot]

Code Review ✅ Approved

Updates the avatar navigation Playwright test to wait for the popover user display name to resolve before capturing it, fixing flaky test assertions. No issues found.

Options

Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Compact

gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Powered by Gitar — free for open source}

[github-actions]

Changes have been cherry-picked to the 1.13 branch.