[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=13602596#comment-13602596 ] 

Stetson Robinson commented on DROOLS-2706:
------------------------------------------

I agree with [~uxdlc]. Cucumber's term is even more confusing.

[~ibek], you say "I'd like to get a simulation word in there to tell that the tool is not just for testing but also for simulating in various environments...etc." I don't know what you mean. Why else would you simulate a scenario except to test that the assets involved function as expected? To me, a scenario is only for testing. What's a non-testing use case for `.scenario` files?

Here's the user's workflow: In a `.scenario` file, I create one or more scenarios involving given facts or conditions and expected outcomes as a result, based on my assets I've created (rules, DMN models, processets, whatever). Then I click "Run Scenario" (or whatever we want to call it) to validate that my assets involved in this scenario function as expected. So I created a scenario and I ran it.

Is that it, in a nutshell? If so, to me, that's a method to test assets by using a defined scenario, a.k.a., a *Test Scenario*. I'm certainly open to other suggestions, but still don't see another use case for scenarios other than testing in one form or another.

> 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)