[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:all-tabpanel ]

Elizabeth Clayton updated DROOLS-4746:
--------------------------------------
    Description: 
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 Scenario test for a single test scenario against a single DMN decision (node) from directly 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. 
* Understand that the inline "quick test" does not persist unless they explicitly Save the test to a new or existing Test Scenario. 
* Save the "quick test" to a new or existing Test Scenario. 


  was:
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.



> 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
>
> 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 Scenario test for a single test scenario against a single DMN decision (node) from directly 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. 
> * Understand that the inline "quick test" does not persist unless they explicitly Save the test to a new or existing Test Scenario. 
> * Save the "quick test" to a new or existing Test Scenario. 



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