From 03ee28b6b282ac3d827413e8f5b10cf990f5e3e3 Mon Sep 17 00:00:00 2001 From: Amardeepsingh Siglani Date: Sat, 17 Feb 2024 04:05:39 +0530 Subject: [PATCH] [Security analytics] add force option to avoid element getting covered error (#1102) Signed-off-by: Amardeepsingh Siglani (cherry picked from commit eb10f07eb247aac71d08f4d96920be88b4125ddf) --- .../security-analytics-dashboards-plugin/2_rules.spec.js | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cypress/integration/plugins/security-analytics-dashboards-plugin/2_rules.spec.js b/cypress/integration/plugins/security-analytics-dashboards-plugin/2_rules.spec.js index 4b6fa5774..b1831cfc9 100644 --- a/cypress/integration/plugins/security-analytics-dashboards-plugin/2_rules.spec.js +++ b/cypress/integration/plugins/security-analytics-dashboards-plugin/2_rules.spec.js @@ -517,7 +517,7 @@ describe('Rules', () => { ); toastShouldExist(); getSelectionPanelByIndex(0).within(() => - getMapValueField().type('FieldValue') + getMapValueField().type('FieldValue', { force: true }) ); // selection map list field @@ -528,7 +528,7 @@ describe('Rules', () => { toastShouldExist(); getSelectionPanelByIndex(0).within(() => { getListRadioField().click({ force: true }); - getMapListField().type('FieldValue'); + getMapListField().type('FieldValue', { force: true }); }); // condition field