December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3397) Move undoable logic to AbstractCommand

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3397?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-3397: ------------------------------------ Labels: drools-tools (was: ) > Move undoable logic to AbstractCommand > -------------------------------------- > > Key: DROOLS-3397 > URL: https://issues.redhat.com/browse/DROOLS-3397 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Minor > Labels: drools-tools > > Move undoable logic from AbstractScenarioSimulationCommand to AbstractCommand. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3992) Improving error messages from backend to cell popover

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3992?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-3992: ------------------------------------ Labels: ScenarioSimulation drools-tools (was: ScenarioSimulation) > Improving error messages from backend to cell popover > ------------------------------------------------------ > > Key: DROOLS-3992 > URL: https://issues.redhat.com/browse/DROOLS-3992 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.22.0.Final > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Minor > Labels: ScenarioSimulation, drools-tools > > Aim of this ticket: > - Improve error messages sent by server to the cell popover in case of specific errors: eg. > [~kkufova]: I noticed that Impossible to parse as boolean message keeps getting displayed instead of an actual help. For example, I used falsee instead of false. I think in this case we definitely need The expected value is 'false' but the actual one is 'falsee'. Another scenario: if the expected value is null but I enter [] instead, the error message is Error with this value: Impossible to parse as boolean. It doesn't say anything about the actual value being null. > - Improving exceptions handling related to this part: at the moment, any type of exception could be sent to the popover (eg. OutOfMemory). Only a subset should be managed. > Related to https://issues.jboss.org/browse/DROOLS-3838 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4586) Editing mode do not moves displayed part of grid to view the entire scenario description cell

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4586?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4586: ------------------------------------ Labels: CustomerFocus drools-tools (was: CustomerFocus) > Editing mode do not moves displayed part of grid to view the entire scenario description cell > --------------------------------------------------------------------------------------------- > > Key: DROOLS-4586 > URL: https://issues.redhat.com/browse/DROOLS-4586 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.28.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Minor > Labels: CustomerFocus, drools-tools > Attachments: image-2019-10-01-12-18-19-311.png > > > !image-2019-10-01-12-18-19-311.png|thumbnail! > Failure > The input text is hidden by the panel even if it is currently in edit mode, so edited text is hidden -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3799) Check and fix i18n

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3799?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-3799: ------------------------------------ Labels: ScenarioSimulation drools-tools (was: ScenarioSimulation) > Check and fix i18n > ------------------ > > Key: DROOLS-3799 > URL: https://issues.redhat.com/browse/DROOLS-3799 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > > Check that i18n works for all widgets (menu, rightpanel, cheatsheet, etc) and eventually fix it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4699) Supporting long value input

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4699?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4699: ------------------------------------ Labels: drools-tools (was: ) > Supporting long value input > --------------------------- > > Key: DROOLS-4699 > URL: https://issues.redhat.com/browse/DROOLS-4699 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > > Description here: > https://issues.jboss.org/browse/DROOLS-4574?focusedCommentId=13794570&pag... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3730) Add support to DMN constraints on inputs (report input validation errors)

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3730?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-3730: ------------------------------------ Labels: ScenarioSimulation drools-tools (was: ScenarioSimulation) > Add support to DMN constraints on inputs (report input validation errors) > ------------------------------------------------------------------------- > > Key: DROOLS-3730 > URL: https://issues.redhat.com/browse/DROOLS-3730 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation, drools-tools > > See this example https://github.com/kiegroup/drools/compare/master...tarilabs:tarilabs-201... > and try with a value out of the domain ranga [0..100]. > when a Decision or any evaluation which depends on such InputData is triggered, an error message like the following is reported > ```Error while evaluating node 'my decision' for dependency 'my input': the dependency value '999' is not allowed by the declared type (DMNType{ http://www.trisotech.com/definitions/_7ab67159-21c7-4985-91fc-f0d0174898db : tNumber0100 })``` > NOTE: Verify also running the tests from the command line. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4838) Create common producer for tests

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4838?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4838: ------------------------------------ Labels: drools-tools (was: ) > Create common producer for tests > -------------------------------- > > Key: DROOLS-4838 > URL: https://issues.redhat.com/browse/DROOLS-4838 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Minor > Labels: drools-tools > > Inside the tests there is a whole bunch of mocked objects that are used in multiple places (especially the ones related to grid/cell/rendering stuff). > Scope of this ticket shuold be to put all of them inside a static producer; this would also reduce the needs for abstract/inheritance chains, simplifying the test environment -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3100) Expose public API to define fluent scenario

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3100?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-3100: ------------------------------------ Labels: drools-tools (was: ) > Expose public API to define fluent scenario > ------------------------------------------- > > Key: DROOLS-3100 > URL: https://issues.redhat.com/browse/DROOLS-3100 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: drools-tools > > As user I want to be able to extend and define scenario via code using an API -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1989) Test scenarios: Firing a MVEL rule, whose salience is java.lang.Long.MAX_VALUE, in Guvnor

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-1989?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-1989: ------------------------------------ Labels: drools-tools (was: ) > Test scenarios: Firing a MVEL rule, whose salience is java.lang.Long.MAX_VALUE, in Guvnor > ----------------------------------------------------------------------------------------- > > Key: DROOLS-1989 > URL: https://issues.redhat.com/browse/DROOLS-1989 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 5.5.0.Final > Reporter: Hisao Furuichi > Priority: Major > Labels: drools-tools > Attachments: repository_export.xml > > > Problem to fire a MVEL rule, whose salience is 9223372036854775807, in Guvnor. The value 9223372036854775807 is java.lang.Long.MAX_VALUE. If I run a test program in JBDS, I can run without any Exception. > Additional info: > If I change a dialect of the rule from "mvel" to "java", I can run the test without any Exception. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4045) Refactor ScenarioSimulationXMLPersistenceTest

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4045?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4045: ------------------------------------ Labels: ScenarioSimulation drools-tools (was: ScenarioSimulation) > Refactor ScenarioSimulationXMLPersistenceTest > --------------------------------------------- > > Key: DROOLS-4045 > URL: https://issues.redhat.com/browse/DROOLS-4045 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > > Most of the existing tests in {{ScenarioSimulationXMLPersistenceTest}} are trying to test a single step of the migration and not the whole process. Move single step tests to {{InMemoryMigrationStrategyTest}} and keep in {{ScenarioSimulationXMLPersistenceTest}} only end to end migration testing -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 December 2019