[jboss-jira] [JBoss JIRA] (DROOLS-4746) UX for DMN "quick test" tool

[Elizabeth Clayton (Jira)]

    [ https://issues.redhat.com/browse/DROOLS-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029340#comment-14029340 ] 

Elizabeth Clayton commented on DROOLS-4746:
-------------------------------------------

[~karreiro][~danielezonca][~tirelli] I updated the click-thru based on feedback from [~danielezonca]. Changes include:
- Grouped input sections that are collapsible, with labels that present an icon to describe the node type.
- Grouped input section labels that are hyperlinked and will navigate the user to the model, with the respective node properties panel open. 
- Open "inspect" panel via 3 means: Left-click select the table, right-click contextual menu on table header cells, toolbar button. 
- Changed "boxed expression" language in the panel title and tooltips to "Decision Logic" but needs input/review from [~stetson.robinson] or respective content specialist. 

Updated click-thru:  https://marvelapp.com/7208d3a

> UX for DMN "quick test" tool
> ----------------------------
>
>                 Key: DROOLS-4746
>                 URL: https://issues.redhat.com/browse/DROOLS-4746
>             Project: Drools
>          Issue Type: Story
>          Components: DMN Editor
>            Reporter: Elizabeth Clayton
>            Assignee: Elizabeth Clayton
>            Priority: Major
>              Labels: UX, UXTeam, drools-tools
>         Attachments: Screen Shot 2020-04-08 at 4.34.49 PM.png, Screen Shot 2020-04-08 at 5.01.51 PM.png, Screen Shot 2020-04-09 at 9.29.34 AM.png, decision-logic-2-2.png, decision-logic-3-2.png
>
>
> 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.
> *Acceptance criteria*
> Users are able to:
> * Execute a single node boxed expression by providing node inputs (within the DMN editor.) 
> * Explore the DMN model and provide inputs necessary to run a scenario test.  
> * Obtain results (Expected) within the DMN editor once the test is run. 
> Notes:
> * Try to dissociate this feature from the "test scenario" concept and think of this more as a partial execution. When we're thinking about the concept of a "test scenario", we think about input values and expected outputs... however, in this new component, users will be able to provide inputs and just check the current output.
> * Out of scope: Saving or exporting the "quick test." 



--
This message was sent by Atlassian Jira
(v7.13.8#713008)