tck icon indicating copy to clipboard operation
tck copied to clipboard

Decision Model and Notation Technology Compatibility Kit

Results 22 tck issues
Sort by recently updated
recently updated
newest added

Additional test coverage around ranges

Create transitive import test cases based on the [code snippets in the comments on DMN15-58](https://issues.omg.org/browse/DMN15-58?focusedCommentId=24279&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-24279) Resulting Model: ![image](https://user-images.githubusercontent.com/40038/225106730-cc1f1883-2dbd-4e00-be03-9e9199effccf.png) [resulting-drg.dmn.txt](https://github.com/dmn-tck/tck/files/10972652/resulting-drg.dmn.txt)

Hi all, Regarding the recent `1111-feel-matches-function.dmn` PR. It has a number of tests in it that use a `null` value where an optional function parameter is specified .. like this:...

Test cases for the new feature in DMN 1.6 (Ballot #3): DMN16-11 (https://issues.omg.org/browse/DMN16-11) A new value attribute (number) is added to data, time and duration properties.

Test cases supporting the new FEEL descendant operator: https://issues.omg.org/browse/DMN16-80 Currently on the DMN 1.5 namespace since we don't have a 1.6 namespace yet.

I believe the above test case is not CL3 compliant. Here is the rationale: - According to 2.1 (page 17) "An implementation claiming conformance to Conformance Level 3 SHALL comply...

Here are the test cases to revisit for 1.6: - https://github.com/dmn-tck/tck/pull/592 - https://github.com/dmn-tck/tck/pull/593 - https://github.com/dmn-tck/tck/pull/594 - https://github.com/dmn-tck/tck/pull/595 - https://github.com/dmn-tck/tck/pull/602 - https://github.com/dmn-tck/tck/pull/603 - https://github.com/dmn-tck/tck/pull/604 - https://github.com/dmn-tck/tck/pull/605

There are Python DMN engines, so it would be good to be able to test compliance of such engines too. Investigate the possibility.

enhancement
help wanted

Some of the Optional GHA TCK Runners, ie the Vendor specific ones, are completing **Successfully** (✅ ) even when the test case is clearly wrong. This could be confusing for:...