Added fixme for the audit log tests

[Rohit0301]

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.

[gitar-bot]

💡 Quality: Missing reason/tracking issue for fixme-marked tests

Four tests across two describe blocks are marked as fixme but there's no inline comment or linked issue explaining why they're failing. Playwright's fixme() accepts an optional description string (e.g., test.fixme('reason') or as a second argument) and the PR description uses a placeholder Fixes <issue-number>.

Without context, future developers won't know:

• What failure these tests exhibit
• Whether there's a tracking issue for re-enabling them
• If the root cause is in the test code or the application

This risks the fixme markers becoming permanent technical debt.

Suggested fix:

  test.fixme('should search audit logs', async ({ page }) => {
    // TODO: Skipped due to <issue-link> - search API returns inconsistent results

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

[gitar-bot]

💡 Quality: Redundant test.fixme() inside test.describe.fixme() block

The test 'should include filters and search in export request' at line 816 is individually wrapped with test.fixme(), but it's already inside the test.describe.fixme() block (line 690). When a describe block is marked as fixme, all tests within it are automatically skipped. The inner test.fixme() wrapper (and the associated comment and indentation changes) are unnecessary.

This won't cause any functional issue, but removing the redundant wrapper would simplify the code and avoid the indentation churn (lines 815-882).

Suggested fix:

    test(
      'should include filters and search in export request',
      async ({ page }) => {

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

[gitar-bot]

Code Review 👍 Approved with suggestions 0 resolved / 2 findings

Test-only change correctly disables flaky tests, but still lacks a tracking issue for re-enablement, and one test.fixme() is redundant inside an already-fixme'd describe block.

💡 Quality: Redundant test.fixme() inside test.describe.fixme() block

📄 openmetadata-ui/src/main/resources/ui/playwright/e2e/Pages/AuditLogs.spec.ts:816

The test 'should include filters and search in export request' at line 816 is individually wrapped with test.fixme(), but it's already inside the test.describe.fixme() block (line 690). When a describe block is marked as fixme, all tests within it are automatically skipped. The inner test.fixme() wrapper (and the associated comment and indentation changes) are unnecessary.

This won't cause any functional issue, but removing the redundant wrapper would simplify the code and avoid the indentation churn (lines 815-882).

Suggested fix

    test(
      'should include filters and search in export request',
      async ({ page }) => {

💡 Quality: Missing reason/tracking issue for fixme-marked tests

📄 openmetadata-ui/src/main/resources/ui/playwright/e2e/Pages/AuditLogs.spec.ts:401 📄 openmetadata-ui/src/main/resources/ui/playwright/e2e/Pages/AuditLogs.spec.ts:687 📄 openmetadata-ui/src/main/resources/ui/playwright/e2e/Pages/AuditLogs.spec.ts:812

Four tests across two describe blocks are marked as fixme but there's no inline comment or linked issue explaining why they're failing. Playwright's fixme() accepts an optional description string (e.g., test.fixme('reason') or as a second argument) and the PR description uses a placeholder Fixes <issue-number>.

Without context, future developers won't know:

• What failure these tests exhibit
• Whether there's a tracking issue for re-enabling them
• If the root cause is in the test code or the application

This risks the fixme markers becoming permanent technical debt.

Suggested fix

  test.fixme('should search audit logs', async ({ page }) => {
    // TODO: Skipped due to <issue-link> - search API returns inconsistent results

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.77% (56483/85884)	45.21% (29573/65419)	48.03% (8924/18581)

[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