From 66e2c720fdce430c1f1a92a603b6c7db87301950 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mike=20C=C3=B4t=C3=A9?= Date: Fri, 17 Jan 2020 16:26:09 -0500 Subject: [PATCH] Re-enable mute all test now that API is no longer flaky (#55172) --- .../security_and_spaces/tests/alerting/alerts.ts | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/x-pack/test/alerting_api_integration/security_and_spaces/tests/alerting/alerts.ts b/x-pack/test/alerting_api_integration/security_and_spaces/tests/alerting/alerts.ts index 551498e22d5c..08e6c90a1044 100644 --- a/x-pack/test/alerting_api_integration/security_and_spaces/tests/alerting/alerts.ts +++ b/x-pack/test/alerting_api_integration/security_and_spaces/tests/alerting/alerts.ts @@ -662,16 +662,7 @@ export default function alertTests({ getService }: FtrProviderContext) { } }); - /** - * Skipping due to an issue we've discovered in the `muteAll` api - * which corrupts the apiKey and causes this test to exhibit flaky behaviour. - * Failed CIs for example: - * 1. https://github.com/elastic/kibana/issues/53690 - * 2. https://github.com/elastic/kibana/issues/53683 - * - * This will be fixed and reverted in PR: https://github.com/elastic/kibana/pull/53333 - */ - it.skip(`shouldn't schedule actions when alert is muted`, async () => { + it(`shouldn't schedule actions when alert is muted`, async () => { const testStart = new Date(); const reference = alertUtils.generateReference(); const response = await alertUtils.createAlwaysFiringAction({