July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-279) Pipeline to Istio 0.8.0

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-279?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-279: ------------------------------- Sprint: Kiali QE Sprint 8 (was: Kiali QE Sprint 7) > Pipeline to Istio 0.8.0 > ----------------------- > > Key: SWSQE-279 > URL: https://issues.jboss.org/browse/SWSQE-279 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2696) Dialog to name test and define bindings (UX)

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2696?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2696: ------------------------------------- [~tirelli] [~ibek] Updated the mockups to include an MVP, and two alternatives for a Future. Let me know what you think, thanks. !Add-notsosimpleA.png|thumbnail! !Add-notsosimpleB.png|thumbnail! !Add-simple1.png|thumbnail! !Add-simple1b.png|thumbnail! 2 goals: * Trying to get away from using "rule bindings" and similar lingo, unless the user opts-in to use the Advanced Settings. * Trying to find a path to support future options that requires minimal redesign. Note: the current design reveals options on selection. > Dialog to name test and define bindings (UX) > -------------------------------------------- > > Key: DROOLS-2696 > URL: https://issues.jboss.org/browse/DROOLS-2696 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam > Attachments: Add-notsosimpleA.png, Add-notsosimpleB.png, Add-simple1.png, Add-simple1b.png > > > As a business user I want the ability to name a scenario test and define the rule bindings so that I can create a test asset. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2696) Dialog to name test and define bindings (UX)

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2696?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2696: -------------------------------- Attachment: Add-notsosimpleA.png Add-notsosimpleB.png Add-simple1.png Add-simple1b.png > Dialog to name test and define bindings (UX) > -------------------------------------------- > > Key: DROOLS-2696 > URL: https://issues.jboss.org/browse/DROOLS-2696 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam > Attachments: Add-notsosimpleA.png, Add-notsosimpleB.png, Add-simple1.png, Add-simple1b.png > > > As a business user I want the ability to name a scenario test and define the rule bindings so that I can create a test asset. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2696) Dialog to name test and define bindings (UX)

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2696?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2696: -------------------------------- Attachment: (was: Screen Shot 2018-07-02 at 3.08.48 PM.png) > Dialog to name test and define bindings (UX) > -------------------------------------------- > > Key: DROOLS-2696 > URL: https://issues.jboss.org/browse/DROOLS-2696 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam > Attachments: Add-notsosimpleA.png, Add-notsosimpleB.png, Add-simple1.png, Add-simple1b.png > > > As a business user I want the ability to name a scenario test and define the rule bindings so that I can create a test asset. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2696) Dialog to name test and define bindings (UX)

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2696?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2696: -------------------------------- Attachment: (was: Screen Shot 2018-07-02 at 3.09.02 PM.png) > Dialog to name test and define bindings (UX) > -------------------------------------------- > > Key: DROOLS-2696 > URL: https://issues.jboss.org/browse/DROOLS-2696 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam > Attachments: Add-notsosimpleA.png, Add-notsosimpleB.png, Add-simple1.png, Add-simple1b.png > > > As a business user I want the ability to name a scenario test and define the rule bindings so that I can create a test asset. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

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

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2706?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-2706: --------------------------------------- Just to clarify, the current capabilities being discussed don't have much in the way of simulation, but that is something we would like to add in the future. When we start to deal with CEP and timelines, then the simulation features will start to be required, for instance, to create events at certain points in time, and to control the simulation clock. I am not sure we need to have the terminology in place as of today, but we need to keep in mind the long term goal. > 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)

8 years

1
0
0 / 0

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

by Stetson Robinson (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2706?page=com.atlassian.jira.plugi... ] Stetson Robinson edited comment on DROOLS-2706 at 7/9/18 1:39 PM: ------------------------------------------------------------------ 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. [~tirelli], [~Rikkola], adding you in case you have any insight on this naming discussion. was (Author: stetson.robinson): 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)

8 years

1
0
0 / 0

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

by Stetson Robinson (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2706?page=com.atlassian.jira.plugi... ] 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)

8 years

1
0
0 / 0

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

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2706?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2706: ------------------------------------- [~ibek] Thanks for clarifying! Not sure that even the cucumber term is all that user friendly though, particularly for a non-technical persona. [~stetson.robinson] Wdyt? > 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)

8 years

1
0
0 / 0

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

by Ivo Bek (JIRA)

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

8 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2018