[
https://issues.jboss.org/browse/DROOLS-4026?page=com.atlassian.jira.plugi...
]
Donato Marrazzo commented on DROOLS-4026:
-----------------------------------------
Hi [~jomarko], the main point here is to have a probing tool during the authoring phase:
1. It should be on the side and let the user inspect the DMN model, i.e. the user
understands from the model that there is a threshold of 1000, so s/he can probe with a
value above or under the threshold.
2. Majority of the probes are just a quick experiment in the "try and error"
cycle, so I don't expect the user want to create always a test scenario.
3. While DMN designer builds the model, s/he needs to check the correctness of a partial
model, maybe later when the model will be complete those probing values will be useless or
inconsistent.
The main downsides of the test scenarios for this purpose are:
1. you cannot see at sametime the DMN model
2. you have to put the expected output, whereas you just want to inject inputs and see the
results
Quick test tool useful during DMN authoring
-------------------------------------------
Key: DROOLS-4026
URL:
https://issues.jboss.org/browse/DROOLS-4026
Project: Drools
Issue Type: Epic
Components: DMN Editor
Affects Versions: 7.21.0.Final
Reporter: Donato Marrazzo
Assignee: Michael Anstis
Priority: Major
Labels: Field, drools-tools
As a DMN author, I'd like to probe the DMN model during the authoring phase without
leaving the DMN Editor. Actually, it's really important to explore the DMN model to
understand with values are required by the test.
When the user run the test he can get back the results of the DMN execution.
Moreover, it would be handy to add those input/output to an existing (or new) test
scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)