[
https://issues.redhat.com/browse/DROOLS-4746?page=com.atlassian.jira.plug...
]
Elizabeth Clayton edited comment on DROOLS-4746 at 4/14/20 4:37 PM:
--------------------------------------------------------------------
[~tirelli] [~karreiro]
I updated the [
click-thru|https://marvelapp.com/7208d3a] with the changes discussed:
- Added "Inspect" and "View properties" to "Clear" option in
the menu the user gets when selecting the table/grid. I placed these in a left-click
popover menu. The same option could be added to the right click contextual menu as well.
- I removed the Inspect menu option for the right click contextual menu at the header cell
level, because the action is already covered by the table select action.
- I changed the "Test" button label to "Inspect" because I believe
that I heard that was a more accurate description of the action.
- I looked for alternative fontawesome icons to replace the bug. I found these but I'm
not sure if any of them are better?:
https://fontawesome.com/icons/microscope?style=solid
https://fontawesome.com/icons/binoculars?style=solid
https://fontawesome.com/icons/wpexplorer?style=brands
If not, I can see if someone from visual design could help.
Please let me know if I missed anything, if not I'll go ahead and mark this Resolved.
Thanks!
was (Author: uxdlc):
[~tirelli] [~karreiro]
I updated the click-thru with the changes discussed:
- Added "Inspect" and "View properties" to "Clear" option in
the menu the user gets when selecting the table/grid. I placed these in a left-click
popover menu. The same option could be added to the right click contextual menu as well.
- I removed the Inspect menu option for the right click contextual menu at the header cell
level, because the action is already covered by the table select action.
- I changed the "Test" button label to "Inspect" because I believe
that I heard that was a more accurate description of the action.
- I looked for alternative fontawesome icons to replace the bug. I found these but I'm
not sure if any of them are better?:
https://fontawesome.com/icons/microscope?style=solid
https://fontawesome.com/icons/binoculars?style=solid
https://fontawesome.com/icons/wpexplorer?style=brands
If not, I can see if someone from visual design could help.
Please let me know if this looks complete otherwise, and I'll close the jira, thanks!
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: Fine.png, 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)