Fix strict mode violation in Audit Logs Playwright tests

[harsh-vador]

Describe your changes:

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 Playwright strict mode violations:
  • Added .first() to date picker cell selectors to resolve ambiguous element matching in date range selection tests
  • Improved waitForResponse filtering with specific URL endpoints and query parameters to prevent false response interception (e.g., userName=admin, entityType= checks)
  • Enhanced test reliability for user filter, entity type filter, and export functionality workflows

_{This will update automatically on new commits.}

[github-actions]

Jest test Coverage

UI tests summary

Lines	Statements	Branches	Functions
	65.74% (56404/85804)	45.17% (29537/65389)	47.98% (8906/18561)

[gitar-bot]

Code Review ✅ Approved 1 resolved / 1 findings

Clean test fix: more specific API response matching and .first() for strict mode compliance. The previous lowerCase() issue is resolved — the problematic call has been removed. No new issues found.

✅ 1 resolved

✅ Bug: lowerCase() breaks URL matching for multi-word entity types

📄 openmetadata-ui/src/main/resources/ui/playwright/e2e/Pages/AuditLogs.spec.ts:352
Lodash's lowerCase() converts strings to space-separated lowercase words, not simple lowercase. For example:

• lowerCase("Table") → "table" ✓
• lowerCase("Database Service") → "database service" ✗ (the URL has entityType=databaseService)

The test reads the display label from .dropdown-option-label (which renders option.label — e.g., "Database Service"), then uses lowerCase() to match against the URL query parameter (which uses option.key — e.g., "databaseService").

This works for single-word entity types but will fail for multi-word ones like "Database Service", "Search Index", "Dashboard Data Model", "Glossary Term", etc. Since the test picks the first item from the dropdown, whether it fails depends on the test environment's data — making this a latent source of flakiness.

Consider using toLower from lodash (which doesn't add spaces: toLower("Database Service") → "database service") — but that still won't match databaseService. A more robust approach would be to use a case-insensitive URL check, or better yet, extract the entity type key from the dropdown option's data attribute rather than its display text.

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}

[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