From ea731bac5c0cca57c47e79908e1e70e9e24d1cc7 Mon Sep 17 00:00:00 2001 From: Darin Kelkhoff Date: Fri, 24 Feb 2023 17:03:56 -0600 Subject: [PATCH] Fix test for step without name (enricher now handles) --- .../backend/core/instances/QInstanceValidatorTest.java | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/qqq-backend-core/src/test/java/com/kingsrook/qqq/backend/core/instances/QInstanceValidatorTest.java b/qqq-backend-core/src/test/java/com/kingsrook/qqq/backend/core/instances/QInstanceValidatorTest.java index 0bedf9ae..61f803bf 100644 --- a/qqq-backend-core/src/test/java/com/kingsrook/qqq/backend/core/instances/QInstanceValidatorTest.java +++ b/qqq-backend-core/src/test/java/com/kingsrook/qqq/backend/core/instances/QInstanceValidatorTest.java @@ -347,11 +347,11 @@ class QInstanceValidatorTest extends BaseTest @Test public void test_validateProcessStepWithEmptyName() { - assertValidationFailureReasons((qInstance) -> qInstance.getProcess(TestUtils.PROCESS_NAME_GREET_PEOPLE).getStepList().get(0).setName(""), - "Missing name for a step"); - - assertValidationFailureReasons((qInstance) -> qInstance.getProcess(TestUtils.PROCESS_NAME_GREET_PEOPLE_INTERACTIVE).getStepList().get(1).setName(null), - "Missing name for a step"); + /////////////////////////////////////////////////////////////////////////////////////////////////////////////////// + // these used to be an assertion failure - but enricher now sets a default name for backend steps w/ a code name // + /////////////////////////////////////////////////////////////////////////////////////////////////////////////////// + assertValidationSuccess((qInstance) -> qInstance.getProcess(TestUtils.PROCESS_NAME_GREET_PEOPLE).getStepList().get(0).setName("")); + assertValidationSuccess((qInstance) -> qInstance.getProcess(TestUtils.PROCESS_NAME_GREET_PEOPLE_INTERACTIVE).getStepList().get(1).setName(null)); }