Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-8462

Stunner - old marshaller tests for AdHocSubProcess are failing

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • 7.22.0.Final
    • Designer
    • NEW
    • NEW

    Description

      Old marshaller tests for AdHocSubProcess are failing.

      The tests are in the class: org.kie.workbench.common.stunner.bpmn.backend.service.diagram.marshalling.subprocesses.AdHocSubProcessTest

      • testUnmarshallTopLevelEmptyPropertiesSubProcess() and testUnmarshallSubProcessLevelEmptyPropertiesSubProcess() are failing because:
        adHocCompletionCondition script is null instead of "".
      • Tests testMarshallTopLevelEmptyPropertiesSubProcess() and testMarshallSubProcessLevelEmptyPropertiesSubProcess() are failing because:
        Node before marshalling has adHocCompletionCondition script set to null and after marshalling it is set to autocomplete.
      • testMarshallTopLevelFilledPropertiesSubProcess() test is failing because there are different process data before and after marshalling:
        • "subVarString:String,subVarCustom:CustomType,subVarBoolean:Boolean,subVarFloat:Float,subVarInteger:Integer,subVarObject:Object"
        • "subVarString,subVarCustom,subVarBoolean,subVarFloat,subVarInteger,subVarObject"

      Attachments

        Issue Links

          is caused by

          Task - Represents a small unit of work that is not end-user facing. JBPM-8367 Stunner - Add marshaller test cases for Adhoc sub-process

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBPM-8467 Stunner - Old marshaller tests for Event and Multiple Instance sub-processes are failing

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              romartin@redhat.com Roger Martinez
              lterifaj@redhat.com Lubomir Terifaj
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: