January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1995) Test Scenarios: Warning for non existent ksession does not disappear when an existing ksession is selected

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1995?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1995. ------------------------------- Resolution: Rejected This wont't be implemented due to newer version of Test Scenarios editor (Preview). > Test Scenarios: Warning for non existent ksession does not disappear when an existing ksession is selected > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1995 > URL: https://issues.jboss.org/browse/DROOLS-1995 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Priority: Minor > > # Make two ksessions: > ## KSessionOne > ## KSessionRemoveMe > # Both need to stateful with a pseudo clock. > # Make a Test scenario. Use KSessionRemoveMe in the test scenario. > # Save and close the test scenario. > # Remove KSessionRemoveMe. > # Reopen the test scenario. You see a warning "KSession does not exist" > # Select KSessionOne > The error message should disappear. > Instead it still shows. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1981) KIE Workbench Test Scenario problems when using Float field in fact expectation

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1981?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1981. ------------------------------- Resolution: Rejected This wont't be implemented due to newer version of Test Scenarios editor (Preview). > KIE Workbench Test Scenario problems when using Float field in fact expectation > ------------------------------------------------------------------------------- > > Key: DROOLS-1981 > URL: https://issues.jboss.org/browse/DROOLS-1981 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 6.4.0.Final > Environment: CentOS > Reporter: Jeff Jensen > Priority: Major > Labels: KIEWorkBench, TestScenario > > Running a KIE Workbench Test Scenario that expects on a Float field type incorrectly fails on values such as "0.8" and ".8". Only values such as "1.0" pass. > Using a Double field does not have this problem. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1991) Test Scenarios: Integer fields should accept empty fields if they are set in the test scenario XML

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1991?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1991. ------------------------------- Resolution: Rejected This wont't be implemented due to newer version of Test Scenarios editor (Preview). > Test Scenarios: Integer fields should accept empty fields if they are set in the test scenario XML > -------------------------------------------------------------------------------------------------- > > Key: DROOLS-1991 > URL: https://issues.jboss.org/browse/DROOLS-1991 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Mark Coble > Priority: Major > > If there is no value set for the field, NumberFormatException will be thrown when running the test scenario. > Cheese.amount = "" > For legacy reasons, we should just ignore these. Because we allowed the users to create XML-files like these. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1853) Rule Asset: Show the old test scenario results where this rule was used.

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1853?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1853. ------------------------------- Resolution: Rejected This wont't be implemented due to newer version of Test Scenarios editor (Preview). > Rule Asset: Show the old test scenario results where this rule was used. > ------------------------------------------------------------------------ > > Key: DROOLS-1853 > URL: https://issues.jboss.org/browse/DROOLS-1853 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor > Reporter: Toni Rikkola > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3019) [DMN Designer] Data Types - Constraints - Range component

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3019?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3019: --------------------------------------- Description: - When "Range" is selected in the Constraints dialog, the following component must be loaded; !prototype.png|thumbnail! - The component contains only two raw input fields and two dropdowns; - The component should be able to store only the min value - The component should be able to store only the max value - The component should be able to store the mix and the max value This component must be made considering that in the future, each kind of data will support a specific component (see the following example considering {{date}}): !future.png|thumbnail! ⚠️ This JIRA does not comprehends the widget that appears in the {{future.png}} file. This JIRA comprehends the only what appears in the {{prototype.png}} file. was: - When "Range" is selected in the Constraints dialog, the following component must be loaded in the dialog; !prototype.png|thumbnail! - The component contains only two raw input fields and two dropdowns; - The component should be able to store only the min value - The component should be able to store only the max value - The component should be able to store the mix and the max value This component must be made considering that in the future, each kind of data will support a specific component (see the following example considering {{date}}): !future.png|thumbnail! ⚠️ This JIRA does not comprehends the widget that appears in the {{future.png}} file. This JIRA comprehends the only what appears in the {{prototype.png}} file. > [DMN Designer] Data Types - Constraints - Range component > --------------------------------------------------------- > > Key: DROOLS-3019 > URL: https://issues.jboss.org/browse/DROOLS-3019 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: future.png, prototype.png > > > - When "Range" is selected in the Constraints dialog, the following component must be loaded; > !prototype.png|thumbnail! > - The component contains only two raw input fields and two dropdowns; > - The component should be able to store only the min value > - The component should be able to store only the max value > - The component should be able to store the mix and the max value > This component must be made considering that in the future, each kind of data will support a specific component (see the following example considering {{date}}): > !future.png|thumbnail! > ⚠️ This JIRA does not comprehends the widget that appears in the {{future.png}} file. This JIRA comprehends the only what appears in the {{prototype.png}} file. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2016) In test scenario, when multiple instances of one class are created, to set a field value to null, instead of entering "=null", give the possibility to set "is null"

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2016?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-2016. ------------------------------- Resolution: Rejected This wont't be implemented due to newer version of Test Scenarios editor (Preview). > In test scenario, when multiple instances of one class are created, to set a field value to null, instead of entering "=null", give the possibility to set "is null" > -------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2016 > URL: https://issues.jboss.org/browse/DROOLS-2016 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Affects Versions: 5.5.0.Final > Reporter: Nicolas Heron > Priority: Major > Attachments: Capture.png > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3021) [DMN Designer] Data Types - Constraints - Enumeration option component

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3021?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3021: --------------------------------------- Description: - When "Enumeration" is selected in the Constraints dialog, the following component must be loaded; !prototype.png|thumbnail! - The component contains a dynamic list to insert the possible values - The input is a simple input without any validation This component must be made considering that in the future, each kind of data will support a specific component (see the following example considering {{date}}): !future.png|thumbnail! ⚠️ This JIRA does not comprehends the widget that appears in the {{future.png}} file. This JIRA comprehends the only what appears in the {{prototype.png}} file. was: - When "Enumeration" is selected in the Constraints dialog, the following component must be loaded in the dialog; !prototype.png|thumbnail! - The component contains a dynamic list to insert the possible values - The input is a simple input without any validation This component must be made considering that in the future, each kind of data will support a specific component (see the following example considering {{date}}): !future.png|thumbnail! ⚠️ This JIRA does not comprehends the widget that appears in the {{future.png}} file. This JIRA comprehends the only what appears in the {{prototype.png}} file. > [DMN Designer] Data Types - Constraints - Enumeration option component > ---------------------------------------------------------------------- > > Key: DROOLS-3021 > URL: https://issues.jboss.org/browse/DROOLS-3021 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: future.png, prototype.png > > > - When "Enumeration" is selected in the Constraints dialog, the following component must be loaded; > !prototype.png|thumbnail! > - The component contains a dynamic list to insert the possible values > - The input is a simple input without any validation > This component must be made considering that in the future, each kind of data will support a specific component (see the following example considering {{date}}): > !future.png|thumbnail! > ⚠️ This JIRA does not comprehends the widget that appears in the {{future.png}} file. This JIRA comprehends the only what appears in the {{prototype.png}} file. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3511) UX Design for additional options for "create scenario" asset dialog

by tao zhu (Jira)

[ https://issues.jboss.org/browse/DROOLS-3511?page=com.atlassian.jira.plugi... ] tao zhu edited comment on DROOLS-3511 at 1/14/19 7:32 AM: ---------------------------------------------------------- The drop-down selector to select Source Type https://redhat.invisionapp.com/share/62PYJV7J9E3 was (Author: zhutaojiajia): The drop-down selector to select Source Type https://redhat.invisionapp.com/share/W5PYJQUSNC2 > UX Design for additional options for "create scenario" asset dialog > ------------------------------------------------------------------- > > Key: DROOLS-3511 > URL: https://issues.jboss.org/browse/DROOLS-3511 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Amy Glass > Assignee: tao zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: TestScenarioPreviewDEVversion.png > > > Add configuration options to the "Create New Test Scenario" dialog. > There should be a drop-down selector to select Source Type. > Currently, the values in the drop-down will be Rule and DMN, but this list can grow. > Once the user selects a value, depending on the source selected, the user may need to specify more information, such as a file name. > Drools-2696 includes an initial MVP design. This issue is created to expand upon that design to support additional configuration options. > [~dzonca] [~tirelli] [~ibek] Please add additional details if possible. Thank you. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3021) [DMN Designer] Data Types - Constraints - Enumeration option component

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3021?page=com.atlassian.jira.plugi... ] Guilherme Carreiro reassigned DROOLS-3021: ------------------------------------------ Assignee: Daniel José dos Santos (was: Guilherme Carreiro) > [DMN Designer] Data Types - Constraints - Enumeration option component > ---------------------------------------------------------------------- > > Key: DROOLS-3021 > URL: https://issues.jboss.org/browse/DROOLS-3021 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: future.png, prototype.png > > > - When "Enumeration" is selected in the Constraints dialog, the following component must be loaded; > !prototype.png|thumbnail! > - The component contains a dynamic list to insert the possible values > - The input is a simple input without any validation > This component must be made considering that in the future, each kind of data will support a specific component (see the following example considering {{date}}): > !future.png|thumbnail! > ⚠️ This JIRA does not comprehends the widget that appears in the {{future.png}} file. This JIRA comprehends the only what appears in the {{prototype.png}} file. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1996) Test Scenario Indexing broken

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1996?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1996. ------------------------------- Resolution: Done This wont't be implemented due to newer version of Test Scenarios editor (Preview). > Test Scenario Indexing broken > ----------------------------- > > Key: DROOLS-1996 > URL: https://issues.jboss.org/browse/DROOLS-1996 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 6.4.0.Beta2 > Reporter: Michael Anstis > Assignee: Guilherme Carreiro > Priority: Major > > I built kie-drools-wb locally and ran on EAP6.4 (with .niogit and .index deleted). > The start log contains (lots) of these type of error (probably one for each Test Scenario):- > {code} > 16:05:21,732 ERROR [org.drools.workbench.screens.testscenario.backend.server.indexing.TestScenarioFileIndexer] (EJB default - 7) Unable to index 'default://master@uf-playground/mortgages/src/test/resources/org/mortgages/Pricing%20low%20end.scenario'.: java.lang.NullPointerException > at org.drools.workbench.screens.testscenario.backend.server.indexing.TestScenarioIndexVisitor.getFieldFullyQualifiedClassName(TestScenarioIndexVisitor.java:158) [drools-wb-test-scenario-editor-backend-6.4.0-SNAPSHOT.jar:6.4.0-SNAPSHOT] > at org.drools.workbench.screens.testscenario.backend.server.indexing.TestScenarioIndexVisitor.visit(TestScenarioIndexVisitor.java:105) [drools-wb-test-scenario-editor-backend-6.4.0-SNAPSHOT.jar:6.4.0-SNAPSHOT] > at org.drools.workbench.screens.testscenario.backend.server.indexing.TestScenarioIndexVisitor.visit(TestScenarioIndexVisitor.java:79) [drools-wb-test-scenario-editor-backend-6.4.0-SNAPSHOT.jar:6.4.0-SNAPSHOT] > at org.drools.workbench.screens.testscenario.backend.server.indexing.TestScenarioIndexVisitor.visit(TestScenarioIndexVisitor.java:74) [drools-wb-test-scenario-editor-backend-6.4.0-SNAPSHOT.jar:6.4.0-SNAPSHOT] > at org.drools.workbench.screens.testscenario.backend.server.indexing.TestScenarioIndexVisitor.visit(TestScenarioIndexVisitor.java:68) [drools-wb-test-scenario-editor-backend-6.4.0-SNAPSHOT.jar:6.4.0-SNAPSHOT] > at org.drools.workbench.screens.testscenario.backend.server.indexing.TestScenarioFileIndexer.toKObject(TestScenarioFileIndexer.java:81) [drools-wb-test-scenario-editor-backend-6.4.0-SNAPSHOT.jar:6.4.0-SNAPSHOT] > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

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 January 2019