[Red Hat JIRA] (DROOLS-6017) Move test cases from drools-mvel to drools-test-coverage : 3rd round
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-6017?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-6017:
-----------------------------------
Sprint: 2021 Week 04-06 (from Jan 25), 2021 Week 07-09 (from Feb 15) (was: 2021 Week 04-06 (from Jan 25))
> Move test cases from drools-mvel to drools-test-coverage : 3rd round
> --------------------------------------------------------------------
>
> Key: DROOLS-6017
> URL: https://issues.redhat.com/browse/DROOLS-6017
> Project: Drools
> Issue Type: Task
> Components: core engine, executable model
> Affects Versions: 7.49.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> DROOLS-5972 moved most of CommonTestMethodBase based tests (81 tests) from drools-mvel to drools-test-coverage.
> This JIRA is to evaluate remaining tests in drools-mvel and probably some DRL based tests can be moved to drools-test-coverage. Also we may discuss where the other tests should be moved to. (DROOLS-5866 will move some of them)
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-6029) Unable to build project inserting and updating a fact of same rule running with an executable model
by Abhijit Humbe (Jira)
[ https://issues.redhat.com/browse/DROOLS-6029?page=com.atlassian.jira.plug... ]
Abhijit Humbe moved RHDM-1608 to DROOLS-6029:
---------------------------------------------
Component/s: core engine
executable model
(was: BRE)
Docs QE Status: NEW
Key: DROOLS-6029 (was: RHDM-1608)
QE Status: NEW
Affects Version/s: (was: 7.9.0.GA)
(was: 7.9.1.GA)
Workflow: GIT Pull Request workflow (was: CDW with docs v1)
Environment: (was: * Red Hat Decision Manager
** 7.9.0)
Project: Drools (was: Red Hat Decision Manager)
> Unable to build project inserting and updating a fact of same rule running with an executable model
> ---------------------------------------------------------------------------------------------------
>
> Key: DROOLS-6029
> URL: https://issues.redhat.com/browse/DROOLS-6029
> Project: Drools
> Issue Type: Bug
> Components: core engine, executable model
> Reporter: Abhijit Humbe
> Assignee: Toni Rikkola
> Priority: Major
>
> Customer has rule which look like as:
>
> ~~~
> rule "Testrule"
> dialect "mvel"
> when
> then
> com.Employee e = new Employee();
> e.setId("1");
> insert( e );
> e.setName("abc");
> update( e );
> end
> ~~~
>
> If we try to build project it fails with below exception:
> ~~~
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.44.0.Final-redhat-00003:generateModel (default-generateModel) on project RuleIssue_02864136: Execution default-generateModel of goal org.kie:kie-maven-plugin:7.44.0.Final-redhat-00003:generateModel failed.: RuntimeException -> [Help 1]
> [ERROR]
> ~~~
>
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5981) DMN FEEL: arithmetic negation of function leads to null result
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5981?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5981:
-----------------------------------
Sprint: 2021 Week 04-06 (from Jan 25), 2021 Week 07-09 (from Feb 15) (was: 2021 Week 04-06 (from Jan 25))
> DMN FEEL: arithmetic negation of function leads to null result
> --------------------------------------------------------------
>
> Key: DROOLS-5981
> URL: https://issues.redhat.com/browse/DROOLS-5981
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Affects Versions: 7.47.0.Final
> Reporter: Anton Tieleman
> Assignee: Matteo Mortari
> Priority: Minor
> Attachments: ExpressionTest1.dmn, ExpressionTest2.dmn
>
>
> I noticed that a negated expression like {{-sum( 1, 2, 3 )}} leads to a null result on evaluation. According to section 10.3.1.2 (page 111-113) of the [DMN 1.2 specification document|https://www.omg.org/spec/DMN/1.2/PDF] on item 26 "arithmetic negation" it should be possible to prefix a dash to a FEEL function. However, when evaluated, this makes the expression return null. The non-prefixed version as well as 0-expression works as expected.
> This is quite a low priority since there is an easy workaround (prefix 0). I observed this behaviour when running an extensive set of tests to validate conversion from a custom expression language in a client's product to DMN FEEL. I have adjusted the conversion using the workaround.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5876) [Test Scenario Editor] Display actual test results instead of a generic message
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5876?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5876:
-----------------------------------
Sprint: 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25), 2021 Week 07-09 (from Feb 15) (was: 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25))
> [Test Scenario Editor] Display actual test results instead of a generic message
> -------------------------------------------------------------------------------
>
> Key: DROOLS-5876
> URL: https://issues.redhat.com/browse/DROOLS-5876
> Project: Drools
> Issue Type: Enhancement
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Major
> Labels: ScenarioSimulation
>
> In the second row, in the attached test scenario execution result, it gives an error on the List(3) value.
> When I hover over it, I don’t get to see the values of the list, generated by the test scenario, but only this generic message:
> "Error message: Impossible to find elements in the collection to satisfy the conditions"
> It would be handy to see, as, with single values, the list of the actual values generated so that I can compare them with my list of expected values. Now, the user doesn’t have a clue where to look.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5389) Create single abstract class for integration tests in new PMML implementation
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5389?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5389:
-----------------------------------
Sprint: 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7), 2020 Week 40-42 (from Sep 28), 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25), 2021 Week 07-09 (from Feb 15) (was: 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7), 2020 Week 40-42 (from Sep 28), 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25))
> Create single abstract class for integration tests in new PMML implementation
> -----------------------------------------------------------------------------
>
> Key: DROOLS-5389
> URL: https://issues.redhat.com/browse/DROOLS-5389
> Project: Drools
> Issue Type: Task
> Reporter: Jiri Petrlik
> Assignee: Jiri Petrlik
> Priority: Major
> Labels: TrustyAI
>
> Currently there are multiple abstract classes for PMML integration tests such as AbstractPMMLTreeTest, AbstractPMMLRegressionTest etc. The goal of this JIRA is to unify them and create one single abstract class.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5426) Code completion with C3 for FEEL
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5426?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5426:
-----------------------------------
Sprint: 2020 Week 40-42 (from Sep 28), 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25), 2021 Week 07-09 (from Feb 15) (was: 2020 Week 40-42 (from Sep 28), 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25))
> Code completion with C3 for FEEL
> --------------------------------
>
> Key: DROOLS-5426
> URL: https://issues.redhat.com/browse/DROOLS-5426
> Project: Drools
> Issue Type: Feature Request
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
>
> First iteration will more or less match the existing propositions. With some small benefits. For example the correct location detection of the identifiers and functions are improved.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5729) Reorganize drools unit tests
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5729?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5729:
-----------------------------------
Sprint: 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25), 2021 Week 07-09 (from Feb 15) (was: 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25))
> Reorganize drools unit tests
> ----------------------------
>
> Key: DROOLS-5729
> URL: https://issues.redhat.com/browse/DROOLS-5729
> Project: Drools
> Issue Type: Story
> Components: core engine
> Affects Versions: 7.44.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> Motivation: The motivation is to increase test coverage. For example, unit tests which exist under drools-mvel are not tested against executable-model. "Which module is suitable for the unit test?" depends on each test so we may occasionally need to discuss. But basically drools-test-coverage is a good place for DRL based tests because drools-test-coverage may have all dependencies so is flexible to test with any configurations (e.g. alpha compiler network).
> Goals: Increase test coverage. More stable product.
> Impact: During this work, we may find new bugs (because of increased tests). Will need to fix them one-by-one as separated JIRAs.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months