[jboss-jira] [JBoss JIRA] (DROOLS-2706) New "Scenario Test" asset list option (UX)

[Stetson Robinson (JIRA)]

    [ https://issues.jboss.org/browse/DROOLS-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13601574#comment-13601574 ] 

Stetson Robinson edited comment on DROOLS-2706 at 7/6/18 11:38 AM:
-------------------------------------------------------------------

[~uxdlc], [~mstevens1], [~ibek], we should also make sure we all agree on the name for this new asset. Various names are floating around: "Scenario Simulation", "Scenario Test", etc. IMO, I think we should consider *"Rule Scenario Test"* or the like, to make it clearest. Might require additional discussion, which I think we should have.


was (Author: stetson.robinson):
[~uxdlc], [~mstevens1], [~ibek], we should also make sure we all agree on the name for this new asset. Various names are floating around: "Scenario Simulation", "Scenario Test", etc. IMO, I think we should consider *"Rules Scenario Test"* or the like, to make it clearest. Might require additional discussion, which I think we should have.

> New "Scenario Test" asset list option (UX)
> ------------------------------------------
>
>                 Key: DROOLS-2706
>                 URL: https://issues.jboss.org/browse/DROOLS-2706
>             Project: Drools
>          Issue Type: Task
>          Components: Scenario Simulation and Testing
>            Reporter: Liz Clayton
>            Assignee: Liz Clayton
>              Labels: UX, UXTeam
>
> As a practitioner - I want to be able to distinguish the new Scenario Test tool option, from the existing one, within the Asset list so that I can quickly/easily create a test using the new editor.
> *Verification conditions:*
> The new Scenario Test tool is distinguishable from the existing test tool within the asset list, through visual inspection by the user (no hover/click required.)
> Notes:
> Need a way to identify "experimental" tools from existing (to be deprecated?) tools. Solution might include distinct names for each, or parenthetical append (e.g. "experimental, beta, preview...) Or visual indicator, such as an icon, flag, etc.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)