[JBoss JIRA] (SWSQE-275) Add DestinationRule CRUD
by Hayk Hovsepyan (JIRA)
[ https://issues.jboss.org/browse/SWSQE-275?page=com.atlassian.jira.plugin.... ]
Hayk Hovsepyan resolved SWSQE-275.
----------------------------------
Resolution: Done
> Add DestinationRule CRUD
> ------------------------
>
> Key: SWSQE-275
> URL: https://issues.jboss.org/browse/SWSQE-275
> Project: Kiali QE
> Issue Type: Task
> Reporter: Hayk Hovsepyan
> Assignee: Hayk Hovsepyan
>
> Create Destination Rule.
> Read destination rule in Service Details page.
> Read destination rule in Istio Config page.
> Edit destination rule and spoil it. (i.e. set wrong host).
> Verify that it disappears in Service Details and in Istio Config pages.
> Fix back the destination rule.
> Verify that it appears back.
> Delete it.
> Verify that it is removed from both places.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[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 reassigned DROOLS-2706:
-----------------------------------
Assignee: Ivo Bek (was: Gaurav Dey)
> 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: Ivo Bek
> Labels: ScenarioSimulation, 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)
7 years, 11 months
[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:
-------------------------------------
[~g.dey18] I'm going to reassign this to Ivo, seems like it needs broader discussion. Thanks
> 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: Gaurav Dey
> Labels: ScenarioSimulation, 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)
7 years, 11 months