You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kie.apache.org by "AthiraHari77 (via GitHub)" <gi...@apache.org> on 2026/08/26 20:33:39 UTC

[I] Decision Engine: Test Suite targeting Unary Test (1157-unarytests-decisiontable-test-01.xml) failures [incubator-kie]

AthiraHari77 opened a new issue, #6922:
URL: https://github.com/apache/incubator-kie/issues/6922

   Few DMN TCK Tests from 1157-unarytests-decisiontable-test-01.xml Fails. 
   
   [1157-unarytests-decisiontable-test-01.xml](https://github.com/user-attachments/files/23162107/1157-unarytests-decisiontable-test-01.xml)
   
   [1157-unarytests-decisiontable.txt](https://github.com/user-attachments/files/23162121/1157-unarytests-decisiontable.txt)
   
   This ticket focuses on identifying the root cause of errors introduced by the PR https://github.com/dmn-tck/tck/pull/672. Below are the new failing tests introduced by this PR.
   
   ```
   <testCase id="005">
           <description>input values: input expression is not valid against input values and will become null</description>
           <resultNode name="decision005" type="decision">
               <expected>
                   <value xsi:type="xsd:string">success</value>
               </expected>
           </resultNode>
       </testCase>
   
       <testCase id="006">
           <description>input values: input expression is valid against input values - '?' symbol with built-in function</description>
           <!-- also shows input values unary tests can call built-in functions -->
           <resultNode name="decision006" type="decision">
               <expected>
                   <value xsi:type="xsd:string">success</value>
               </expected>
           </resultNode>
       </testCase>
   
       <testCase id="006_a">
           <description>input values: input expression is valid against input values - '?' inside literal string</description>
           <resultNode name="decision006_a" type="decision">
               <expected>
                   <value xsi:type="xsd:string">success</value>
               </expected>
           </resultNode>
       </testCase>
   
       <testCase id="006_b">
           <description>input values: "?" symbol alone is not satisfied</description>
           <resultNode name="decision006_b" type="decision">
               <expected>
                   <value xsi:type="xsd:string">success</value>
               </expected>
           </resultNode>
       </testCase>
   
       <testCase id="006_c">
           <description>input values: "?" symbol alone will be satisfied a true value</description>
           <resultNode name="decision006_c" type="decision">
               <expected>
                   <value xsi:type="xsd:string">success</value>
               </expected>
           </resultNode>
       </testCase>
   
     <testCase id="008">
           <!-- "One of the expressions in the UnaryTests evaluates to true when the implicit value
           is applied to it." -->
           <!-- this test is to exercise the vagueness of 'applied to'.  One of the expressions is simply
           "true".  Which, as an expression always evaluates to true.  So ... should satisfy.  But, in practice,
           the value of "false" applied against unary tests "("123", true)" should not satisfy any of them.  My
           interpretation is that "applied to" is meant for unary comparisons. -->
           <description>input values: boolean expression is weird</description>
           <resultNode name="decision008" type="decision">
               <expected>
                   <value xsi:type="xsd:string">success</value>
               </expected>
           </resultNode>
     </testCase>
   
   <testCase id="008_b">
           <!-- further to 008, an input expression of boolean "false" will not be satisfied against a rule
            unary test of that evaluates to true -->
           <description>input values: boolean expression is weird</description>
           <resultNode name="decision008_b" type="decision">
               <expected>
                   <value xsi:type="xsd:string">success</value>
               </expected>
           </resultNode>
       </testCase>
   
    <testCase id="014">
           <description>output values: multiple columns - column not satisfied</description>
           <resultNode name="decision014" type="decision">
               <expected>
                   <component name="col1">
                       <value xsi:type="xsd:string">foo</value>
                   </component>
                   <component name="col2">
                       <value xsi:nil="true"/>
                   </component>
               </expected>
           </resultNode>
       </testCase>
   
       <testCase id="015">
           <description>output values: ? used in tests - satisfied</description>
           <resultNode name="decision015" type="decision">
               <expected>
                   <value xsi:type="xsd:string">foo</value>
               </expected>
           </resultNode>
       </testCase>
   
   <testCase id="017">
           <description>input values: ? used in expression outside of unary tests expressions</description>
           <resultNode name="decision017" type="decision">
               <expected>
                   <value xsi:type="xsd:string">success</value>
               </expected>
           </resultNode>
       </testCase>
   ```
   
   ```
   1. ERROR: FAILURE: 'decision005' expected='success' but found='null' FIXED
   2. ERROR: FAILURE: 'decision006' expected='success' but found='null'
   3. ERROR: FAILURE: 'decision006_a' expected='success' but found='null' FIXED
   4. ERROR: FAILURE: 'decision006_b' expected='success' but found='null'
   5. ERROR: FAILURE: 'decision006_c' expected='success' but found='null'
   6. ERROR: FAILURE: 'decision008' expected='success' but found='null'
   7. ERROR: FAILURE: 'decision008_b' expected='success' but found='null' FIXED
   8. ERROR: FAILURE: 'decision014' expected='{col2=null, col1=foo}' but found='null'
   9. ERROR: FAILURE: 'decision015' expected='foo' but found='null'
   10. ERROR: FAILURE: 'decision017' expected='success' but found='null'
   
   
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org