Flaky(UI) : Bulk import

[dhruvjsx]

Describe your changes:

Fixes

I worked on ... because ...

Type of change:

• Bug fix
• Improvement
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation

Checklist:

• I have read the CONTRIBUTING document.
• My PR title is Fixes <issue-number>: <short explanation>
• I have commented on my code, particularly in hard-to-understand areas.
• For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

---

Summary by Gitar

• Fixed race conditions:
  • Added loader detachment waits and dropdown visibility checks before clicking manage-button in BulkImport.spec.ts
• Replaced arbitrary timeouts:
  • Changed file upload wait from fixed 500ms to deterministic upload-file-widget hidden state
• Navigation stabilization:
  • Added networkidle wait and scoped locator in DatabaseSchemaClass.visitEntityPage() to prevent clicking breadcrumb elements

_{This will update automatically on new commits.}

---

[gitar-bot]

🔍 CI failure analysis for 8437eea: 272 total test failures across 5 CI jobs show exponential growth pattern (10→16→20→74→152). Only 2 failures are PR-related (missing await in importUtils.ts). The other 270 failures indicate severe CI infrastructure degradation.

Issue

272 Playwright E2E test failures across five CI jobs with exponential escalation:

• Job 1 (3/6): 10 failures
• Job 2 (6/6): 16 failures
• Job 3 (4/6): 20 failures
• Job 4 (2/6): 74 failures (includes 2 PR-related)
• Job 5 (5/6): 152 failures (all unrelated)

Root Cause

PR-Related Failures (2 out of 272)

File: importUtils.ts:106
Issue: Missing await before page.waitForTimeout(500)

This causes 2 BulkImport test failures in Job 4:

1. Bulk Import Export › Database Schema
2. Bulk Import Export › Keyboard Delete selection

The solution is: Add await keyword:

// Current (broken):
page.waitForTimeout(500)

// Should be:
await page.waitForTimeout(500);

Infrastructure Failures (270 out of 272)

Exponential failure growth: 10 → 16 → 20 → 74 → 152

This pattern indicates severe CI environment degradation, not code issues. All 270 failures are in test files that were NOT modified by this PR.

Details

Job 5 (152 failures) - All unrelated to PR:

• Entity.spec.ts (majority: Dashboard, MlModel, Data Model, Worksheet, File, Spreadsheet entities)
• EntityDataConsumer.spec.ts (multiple entity types)
• EntityDataSteward.spec.ts (various entities)

Error patterns in unrelated tests:

• Element visibility: expect(locator).toBeVisible() failed - element(s) not found
• Strict mode violations: getByTestId resolved to 2 elements
• Text matching: expect(locator).toContainText(expected) failed
• Timeouts: page.goto: Timeout 60000ms exceeded
• Browser crashes: Target page, context or browser has been closed

Evidence of CI infrastructure failure:

1. Exponential growth pattern across shards
2. 270 failures in files unchanged by this PR
3. Consistent browser crash and timeout patterns
4. Multiple test suites affected (Entity, Search, Data Quality)
5. 5 out of 6 shards experiencing failures

Likely causes: Resource exhaustion, memory leaks, browser instability, or test interference in the CI environment.

Code Review ⚠️ Changes requested 0 resolved / 1 findings

Good flaky test fixes overall, but the previous finding about missing await on page.waitForTimeout(500) in importUtils.ts remains unresolved and needs to be fixed.

⚠️ Bug: Missing await on page.waitForTimeout()

📄 openmetadata-ui/src/main/resources/ui/playwright/utils/importUtils.ts:87

The page.waitForTimeout(500) call on line 87 is missing the await keyword. Without await, this timeout has no effect - the code immediately proceeds to click the Users tab without waiting, defeating the purpose of adding this stabilization delay.

Impact: The test will not actually wait for the 500ms timeout before proceeding. This could lead to the same flaky behavior the PR is trying to fix.

Suggested fix:

//wait for small duration to stabilize the page
await page.waitForTimeout(500);

Note: While replacing waitForTimeout with explicit condition-based waits (like waitForSelector) is generally preferred (as done elsewhere in this PR), if a timeout is intentionally used here, it must be awaited to function correctly.

Tip

Comment Gitar fix CI or enable auto-apply: gitar auto-apply:on

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[github-actions]

Jest test Coverage

UI tests summary

Lines	Statements	Branches	Functions
	65.87% (55655/84489)	44.97% (28766/63961)	47.83% (8762/18320)

[sonarqubecloud]

Quality Gate passed for 'open-metadata-ui'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud