Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.6.0.GA
Affects Version/s: 7.5.0.GA
Component/s: DMN
Labels:
- ScenarioSimulation
- drools-tools

Story Points:
3
Affects:

Release Notes
Affects Build:
CR1
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Fix Build:
CR1
Release Note Text:

Hide
Issue: User has possibility to test DMN context expressions using Test Scenario designer. The required format of DMN expressions in Test Scenario designer is:

{"key_a" : "value_a", "key_b" : "value_b", ...}
. However if the test fail, the Test Scenario designer "correct value" feature corrects the value using different format:

{key_a : value_a, key_b : value_b, ...}
. We can spot missing double quotes.
Expected result: "correct value" feature fix the DMN context value with correct format
Actual result: "correct value" feature fix ther DMN context value with wrong format - missing double quotes

Show
Issue: User has possibility to test DMN context expressions using Test Scenario designer. The required format of DMN expressions in Test Scenario designer is: {"key_a" : "value_a", "key_b" : "value_b", ...} . However if the test fail, the Test Scenario designer "correct value" feature corrects the value using different format: {key_a : value_a, key_b : value_b, ...} . We can spot missing double quotes. Expected result: "correct value" feature fix the DMN context value with correct format Actual result: "correct value" feature fix ther DMN context value with wrong format - missing double quotes
Target Release:

7.6.0.GA
Git Pull Request:
https://github.com/kiegroup/drools/pull/2640
Steps to Reproduce:
1. Import the project into business central
2. Run key value test

Sprint:
2019 Week 44-46 (from Okt 28)

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

In the attached project is a test scenario file with two tests. The second one is expected to pass because it is created according to the hint message from the first one while keeping the same input. However it fails.

The issue could be in the suggested syntax of editor: It suggest {key:"value"} however in past we used {"key"="value"}. if that is the case, we should just update suggestion codes in popovers and cheatsheet in the properties panel.