fix(playwright): replace flaky toast assertion with search-based deletion verification in teams & teams drag drop spec

[harsh-vador]

Describe your changes:

Summary

• softDeleteTeam and hardDeleteTeam utilities previously verified deletion via toastNotification, which was flaky in automated tests due to timing — the toast can disappear before the assertion fires.
• Replaced with a deterministic check: after deletion, navigate to the teams listing and search for the deleted team name, asserting empty results via the existing searchTeam(..., { expectEmptyResults: true }) pattern.
• Both utility functions now accept teamName: string as a parameter; all call sites in Teams.spec.ts and TeamsDragAndDrop.spec.ts updated accordingly.

Screen.Recording.2026-04-14.at.1.07.17.PM.mov

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.

[github-actions]

Jest test Coverage

UI tests summary

Lines	Statements	Branches	Functions
	63.88% (59797/93603)	43.64% (31322/71768)	46.73% (9415/20144)

[harsh-vador]

@gitar-bot please review now, the comment is addressed

[gitar-bot]

@gitar-bot please review now, the comment is addressed

Acknowledged! Running the review now.

[harsh-vador]

@gitar-bot review again ,the comment is already addressed

[gitar-bot]

@gitar-bot review again ,the comment is already addressed

Running the review again now!

[gitar-bot]

Code Review ✅ Approved 1 resolved / 1 findings

Replaces flaky toast assertions with search-based verification in the teams and drag-drop specs. This change addresses the ineffective deletion check caused by incorrect name property usage.

✅ 1 resolved

✅ Bug: Passing name instead of displayName makes deletion check ineffective

📄 openmetadata-ui/src/main/resources/ui/playwright/e2e/Pages/Teams.spec.ts:358 📄 openmetadata-ui/src/main/resources/ui/playwright/e2e/Pages/Teams.spec.ts:390 📄 openmetadata-ui/src/main/resources/ui/playwright/utils/team.ts:70-72 📄 openmetadata-ui/src/main/resources/ui/playwright/utils/team.ts:320-334
In Teams.spec.ts lines 358 and 390, teamDetails?.name is passed to softDeleteTeam/hardDeleteTeam, which then calls searchTeam(page, teamName, { expectEmptyResults: true }). The searchTeam function checks link elements using filter({ hasText: teamName }).

However, createTeam() generates different values for name (e.g., pw%team-<uuid>) and displayName (e.g., PW <uuid>). The team listing links display the displayName, not name. So filter({ hasText: name }) will never match any link text, causing matchingCount === 0 to be trivially true — the assertion passes regardless of whether the team was actually deleted.

This defeats the purpose of the new verification approach. Compare with lines 504 and 768 where displayName is correctly used.

Note: For getNewTeamDetails() callers (like TeamsDragAndDrop.spec.ts), name === displayName, so those are fine.

Options

Display: compact → Showing less information.

Comment with these commands to change:

Compact

gitar display:verbose

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

[sonarqubecloud]

Quality Gate passed for 'open-metadata-ui'

Issues
1097 New issues
0 Accepted issues

Measures
14 Security Hotspots
0.0% Coverage on New Code
3.8% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Failed to cherry-pick changes to the 1.12.6 branch.
Please cherry-pick the changes manually.
You can find more details here.