From f555dbef294516517d89e9d41e14b1b2a55425dd Mon Sep 17 00:00:00 2001 From: Milton Hultgren Date: Fri, 24 Nov 2023 12:33:00 +0100 Subject: [PATCH] [infra] Disable flaky ML job ID format test suite (#171915) These tests rely on using browser performance timings to extract URLs used when resolving ML job IDs to check if the right format is used and updated when migrating to the new format. Because this change is transparent to the user there isn't any way to test the behaviour through UI elements and due to the structure of the state management it's not straight forward to test it in isolation. https://github.com/elastic/kibana/issues/171913 has been opened to refactor the state management which should allow for this tests to be updated and re-enabled. --- .../test/functional/apps/infra/logs/ml_job_id_formats/tests.ts | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/x-pack/test/functional/apps/infra/logs/ml_job_id_formats/tests.ts b/x-pack/test/functional/apps/infra/logs/ml_job_id_formats/tests.ts index 9c9c379806d60..06ea712c7ccc0 100644 --- a/x-pack/test/functional/apps/infra/logs/ml_job_id_formats/tests.ts +++ b/x-pack/test/functional/apps/infra/logs/ml_job_id_formats/tests.ts @@ -30,7 +30,8 @@ export default ({ getService, getPageObjects }: FtrProviderContext) => { const requestTracker = createRequestTracker(browser, pageObjects.common); let mlJobHelper: MlJobHelper; - describe('ML job ID formats', function () { + // Disabled until https://github.com/elastic/kibana/issues/171913 is addressed + describe.skip('ML job ID formats', function () { this.beforeAll(async () => { // Access to ml.api has to happen inside a test or test hook mlJobHelper = createMlJobHelper(ml.api);