[JBoss JIRA] (DROOLS-3456) Data type constraints: Number
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3456?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3456:
--------------------------------
Attachment: number-range.png
> Data type constraints: Number
> -----------------------------
>
> Key: DROOLS-3456
> URL: https://issues.jboss.org/browse/DROOLS-3456
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: number-range.png
>
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Number (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3456) Data type constraints: Number
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3456?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3456:
--------------------------------
Attachment: (was: range.png)
> Data type constraints: Number
> -----------------------------
>
> Key: DROOLS-3456
> URL: https://issues.jboss.org/browse/DROOLS-3456
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Number (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (SWSQE-239) Establish Hardware Scenarios to Test (Footprints)
by Guilherme Baufaker Rêgo (Jira)
[ https://issues.jboss.org/browse/SWSQE-239?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-239:
------------------------------------------
Sprint: Kiali QE Sprint 7, Kiali Sprint #16, Kiali Sprint #17 (was: Kiali QE Sprint 7, Kiali Sprint #16, Kiali Sprint #18)
> Establish Hardware Scenarios to Test (Footprints)
> --------------------------------------------------
>
> Key: SWSQE-239
> URL: https://issues.jboss.org/browse/SWSQE-239
> Project: Kiali QE
> Issue Type: Story
> Reporter: Guilherme Baufaker Rêgo
> Assignee: Guilherme Baufaker Rêgo
> Priority: Major
>
> As an administrator, I want to know what is minimum requirements to run Kiali
> As a Kiali Tester, I want to know what is the recommend testing hardware that tests are going to simulate.
> Some notes:
> Minimum requirements to run Kiali (~ 16gb?)
> Action Item: Ask Kevin Corner about customer environment size
> On small openshift cluster?
> One Namespace with Hundreds Services
> Multiple Namespace with Hundreds and 5 Services
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (SWSQE-554) Add missing Openshit API calls
by Guilherme Baufaker Rêgo (Jira)
[ https://issues.jboss.org/browse/SWSQE-554?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-554:
------------------------------------------
Sprint: Kiali Sprint #16, Kiali Sprint #17 (was: Kiali Sprint #16, Kiali Sprint #18)
> Add missing Openshit API calls
> ------------------------------
>
> Key: SWSQE-554
> URL: https://issues.jboss.org/browse/SWSQE-554
> Project: Kiali QE
> Issue Type: Task
> Reporter: Hayk Hovsepyan
> Assignee: Hayk Hovsepyan
> Priority: Major
>
> Currently there are several areas in UI tests that do not have call to Openshift API for data comparison.
> 1. Figure out which calls are missing to Openshift.
> 2. Create API call.
> 3. Create assertions on that results to compare with UI data.
> 4. PR per area (API call).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (SWSQE-239) Establish Hardware Scenarios to Test (Footprints)
by Guilherme Baufaker Rêgo (Jira)
[ https://issues.jboss.org/browse/SWSQE-239?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-239:
------------------------------------------
Sprint: Kiali QE Sprint 7, Kiali Sprint #16, Kiali Sprint #18 (was: Kiali QE Sprint 7, Kiali Sprint #16)
> Establish Hardware Scenarios to Test (Footprints)
> --------------------------------------------------
>
> Key: SWSQE-239
> URL: https://issues.jboss.org/browse/SWSQE-239
> Project: Kiali QE
> Issue Type: Story
> Reporter: Guilherme Baufaker Rêgo
> Assignee: Guilherme Baufaker Rêgo
> Priority: Major
>
> As an administrator, I want to know what is minimum requirements to run Kiali
> As a Kiali Tester, I want to know what is the recommend testing hardware that tests are going to simulate.
> Some notes:
> Minimum requirements to run Kiali (~ 16gb?)
> Action Item: Ask Kevin Corner about customer environment size
> On small openshift cluster?
> One Namespace with Hundreds Services
> Multiple Namespace with Hundreds and 5 Services
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months