Failing test: Chrome X-Pack Observability UI Functional Tests.x-pack/test/observability_functional/apps/observability/pages/alerts/add_to_case·ts - ObservabilityApp Observability alerts / Add to case > When user has read permissions for cases "before all" hook for "does not render case options in the overflow menu"

[kibanamachine]

A test failed on a tracked branch

Error: retry.try timeout: Error: expected http://localhost:5620/app/home#/.includes(http://localhost:5620/app/kibana)
    at common_page.ts:114:15
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at runAttempt (retry_for_success.ts:29:15)
    at retryForSuccess (retry_for_success.ts:68:21)
    at RetryService.try (retry.ts:31:12)
    at CommonPageObject.navigate (common_page.ts:96:5)
    at CommonPageObject.navigateToUrl (common_page.ts:148:5)
    at CommonPageObject.navigateToActualUrl (common_page.ts:205:5)
    at Object.setTestUserRole (users.ts:27:5)
    at Context.<anonymous> (add_to_case.ts:74:9)
    at Object.apply (wrap_function.js:73:16)
    at onFailure (retry_for_success.ts:17:9)
    at retryForSuccess (retry_for_success.ts:59:13)
    at RetryService.try (retry.ts:31:12)
    at CommonPageObject.navigate (common_page.ts:96:5)
    at CommonPageObject.navigateToUrl (common_page.ts:148:5)
    at CommonPageObject.navigateToActualUrl (common_page.ts:205:5)
    at Object.setTestUserRole (users.ts:27:5)
    at Context.<anonymous> (add_to_case.ts:74:9)
    at Object.apply (wrap_function.js:73:16)

First failure: CI Build - main

[elasticmachine]

Pinging @elastic/actionable-observability (Team: Actionable Observability)

[kibanamachine]

New failure: CI Build - main

[kibanamachine]

New failure: CI Build - main

[kibanamachine]

New failure: CI Build - 8.10

[maryam-saeidi]

Based on what I see in the logs, the last two failure is different from the first two, which was fixed by this PR.

In the last two failures, when the redirect to the home page happens, the add integration screen is shown, which should not be the case:

So, we need to check what can lead to seeing this page in some cases and what logic decides whether to show this screen or not.

[maryam-saeidi]

I checked the history of this failure, and it didn't happen in the last 30 days, so I'll close this ticket.