[
https://issues.jboss.org/browse/DROOLS-2706?page=com.atlassian.jira.plugi...
]
Ivo Bek commented on DROOLS-2706:
---------------------------------
[~uxdlc] [~stetson.robinson] Cucumber call them *Executable Specifications*.
https://docs.cucumber.io/ The assets we are considering now are: Business Rules, DMN
Models, and Process Models, (+ maybe Planner if we see a good fit )
What about Set of *Simulation Specifications*? In the dialog "Add a set of Simulation
specifications" .. 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.
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)