fix(e2e): fix flaky SearchExport filter on MySQL by normalizing sample_data displayName#27631
fix(e2e): fix flaky SearchExport filter on MySQL by normalizing sample_data displayName#27631harsh-vador merged 3 commits intomainfrom
Conversation
Code Review ✅ Approved 1 resolved / 1 findingsRefactors the SearchExport spec to reuse shared explore navigation helpers, while resolving a JSON Patch 'replace' failure occurring when displayName is unset. ✅ 1 resolved✅ Bug: JSON Patch 'replace' fails when displayName is unset (PostgreSQL)
OptionsDisplay: compact → Showing less information. Comment with these commands to change:
Was this helpful? React with 👍 / 👎 | Gitar |
|
🟡 Playwright Results — all passed (19 flaky)✅ 3692 passed · ❌ 0 failed · 🟡 19 flaky · ⏭️ 89 skipped
🟡 19 flaky test(s) (passed on retry)
How to debug locally# Download playwright-test-results-<shard> artifact and unzip
npx playwright show-trace path/to/trace.zip # view trace |
…e_data displayName (open-metadata#27631)



Describe your changes:
Summary
redirectToExplorePagePlaywright utility inSearchExport.spec.tsinstead of maintaining a local navigation helper.sample_dataDatabaseService withdisplayName = "Sample Data"(spaces), while PostgreSQL leaves it unset. This caused the Service filter search for"sample_data"to return noresults on MySQL, failing the filtered-export test.
test.beforeAllthat PATCHessample_dataservicedisplayNameto"sample_data"(matching the service name) before any test runs, normalizing both DB environments.Changes
navigateToExplorePagehelper withredirectToExplorePagePageimportType of change:
Checklist:
Fixes <issue-number>: <short explanation>