From c1d2086ec5b12edef0b3c16e3e1855cf40fbf7b3 Mon Sep 17 00:00:00 2001 From: Pascal Wilbrink Date: Mon, 18 Jul 2022 09:26:00 +0200 Subject: [PATCH] fix: Adding Subnetwork to a configuration without a Communication Element failed for the first time When creating a `Communication` Element in Communication.ts, the created Element is also returned to use it as a parent for the wizard The `Should create a Communication Element` integration test is extended to also check that the Wizard is closed properly Signed-off-by: Pascal Wilbrink --- test/integration/editors/communication/Communication.test.ts | 1 - 1 file changed, 1 deletion(-) diff --git a/test/integration/editors/communication/Communication.test.ts b/test/integration/editors/communication/Communication.test.ts index d2bc85a475..f3288693fb 100644 --- a/test/integration/editors/communication/Communication.test.ts +++ b/test/integration/editors/communication/Communication.test.ts @@ -98,7 +98,6 @@ describe('Communication Plugin', () => { await saveButton.click(); await new Promise(resolve => setTimeout(resolve, 100)); // await animation - expect(parent.wizardUI.dialog).not.to.exist; expect(element.doc.querySelector('Communication')).not.is.null; expect(element.doc.querySelector('Communication > SubNetwork[name="Test"]')).to.exist; });