January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1870) [Guided Decision Table] Row with Impossible Match throws Exception

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1870?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1870: --------------------------------- Labels: dtable_testday_preparation qe-test-day reported-by-qe verifier (was: dtable_testday_preparation qe-test-day reported-by-qe) > [Guided Decision Table] Row with Impossible Match throws Exception > ------------------------------------------------------------------ > > Key: DROOLS-1870 > URL: https://issues.jboss.org/browse/DROOLS-1870 > Project: Drools > Issue Type: Sub-task > Affects Versions: 7.0.0.Beta4 > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: dtable_testday_preparation, qe-test-day, reported-by-qe, verifier > Fix For: 7.1.0.Final > > Attachments: Screenshot from 2016-12-12 11-54-51.png > > > Validation of guided decision tables check for rows with 'Impossible Match'. Simple example of such row is one that contains both conditions: > * (p.age < 10) > * (p.age. > 20) > However after such is detected, the attached exception and error dialog is thrown. > Steps to reproduce: > # Create new Guided Decision Table > # Ensure you have available some data object to use > # Lets say you data object is Person with attribute age > # Insert two simple conditions column into table > ** The first condition restricts person age to be less than > ** The second condition restricts person age to be greater than > ** Both conditions are bound to the same fact > # Append row into decision table > ** Set less than condition column to value: 10 > ** Set greater than condition column to value: 20 > # The attached error is thrown > # Expected is Impossible Match detection -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1871) [Guided Decision Table] Date field in simple condition and BRL fragment causes the verification to freeze

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1871?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1871: --------------------------------- Labels: dtable_testday_preparation qe-test-day reported-by-qe verifier (was: dtable_testday_preparation qe-test-day reported-by-qe) > [Guided Decision Table] Date field in simple condition and BRL fragment causes the verification to freeze > --------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1871 > URL: https://issues.jboss.org/browse/DROOLS-1871 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta4 > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: dtable_testday_preparation, qe-test-day, reported-by-qe, verifier > Attachments: Screenshot from 2016-12-14 10-54-03.png > > > If in the decision table simple condition based on Date field and any BRL fragment are used together, then the verification freezes as shown in the attachment. > Steps to reproduce: > # Open example mortgages project > # Navigate into org.mortgages package > # Create new Guided Decision Table > # Add simple condition column that check for applicationDate of an Applicant > # Add 5 rows into table and fill them with some values as shown in the attachment > # Add BRL condition column that checks if there exists Applicant of some age > # The verification will freeze as shown in the attachment -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1872) Gap analisys doesn't work with 3 or more ranges

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1872?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1872: --------------------------------- Labels: verifier (was: ) > Gap analisys doesn't work with 3 or more ranges > ----------------------------------------------- > > Key: DROOLS-1872 > URL: https://issues.jboss.org/browse/DROOLS-1872 > Project: Drools > Issue Type: Sub-task > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > Labels: verifier > Fix For: 7.0.0.CR2 > > Attachments: gap1.png, gap2.png > > > When there are 3 (or more) ranges, as in the attached tables, gap analysis produces false negatives. This is because what it currently does is inverting a range and check if it can find another range that entirely subsumes the inverted range. The error is in the fact that the inverted range shouldn't be checked against each of the remaining ranges one by one, but against their union. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1868) [Guided Decision Table] Empty Row message erases some other

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1868?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1868: --------------------------------- Labels: dtable_testday_preparation qe-test-day reported-by-qe verifier (was: dtable_testday_preparation qe-test-day reported-by-qe) > [Guided Decision Table] Empty Row message erases some other > ----------------------------------------------------------- > > Key: DROOLS-1868 > URL: https://issues.jboss.org/browse/DROOLS-1868 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta6 > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Minor > Labels: dtable_testday_preparation, qe-test-day, reported-by-qe, verifier > Attachments: attachment1.png, attachment2.png > > > Occurrence of "Rule is Empty" validation messages erases others. For example "Missing Range" is erased from validation messages if "Rule is Empty" occurs. > Steps for reproduce: > # Create new decision table that will contain "Missing Range" validation messages > ** see the attachment1 > # Add new row into the table > ** see the attachment2 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1869) [Guided Decision Table] ValidationWebWorkerServlet fails to load web worker

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1869?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1869: --------------------------------- Labels: beta5_smoketesting dtable_testday_preparation qe-test-day reported-by-qe verifier (was: beta5_smoketesting dtable_testday_preparation qe-test-day reported-by-qe) > [Guided Decision Table] ValidationWebWorkerServlet fails to load web worker > --------------------------------------------------------------------------- > > Key: DROOLS-1869 > URL: https://issues.jboss.org/browse/DROOLS-1869 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta4 > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Minor > Labels: beta5_smoketesting, dtable_testday_preparation, qe-test-day, reported-by-qe, verifier > > The guided decision tables are not validated. After user clicks on the _Validate_ button, the error [1] appears in the server log. > Steps to reproduce: > # Create new Guided Decision Table > # Add simple Condition column into the table > # Insert new empty row into the table > # Click Validate button > ** Panel with validation results won't appear > ** The error in server log appear > [1] > {code:log} > 10:32:00,313 ERROR [org.drools.workbench.services.verifier.plugin.backend.VerifierWebWorkerServlet] (default task-43) Failed to load verifier web worker. > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1865) Verification reporting: Subsumptant rows hides Deficient rows

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1865?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1865: --------------------------------- Labels: reported-by-qe verifier (was: reported-by-qe) > Verification reporting: Subsumptant rows hides Deficient rows > ------------------------------------------------------------- > > Key: DROOLS-1865 > URL: https://issues.jboss.org/browse/DROOLS-1865 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta7 > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: reported-by-qe, verifier > Attachments: Screenshot from 2017-03-22 09-01-59.png, Screenshot from 2017-03-22 09-02-42.png, deficientAndSubsumptantRows.gdst > > > If the table contains Deficient rows and Subsumptant rows are added, then the messages about Deficient rows disappear. > To reproduce: > # Open the example *mortgages* project > # Navigate into the package: *mortgages.mortgages* > # Upload there the attached GDST > # You will see GDST with 4 rows > ** There will be verification message about Subsumptant rows > # Remove the rows: 3, 4 > # Save and reopen the GDST > ** There won't be verification message about Subsumptant rows > ** There will be verification messages about Deficient rows > ** Messages about Deficient rows are expected also before deleting rows: 3, 4 > The same holds true also if the rows 3 and 4 are Conflicting or Redundant. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1866) Verification reporting: Missing range is thrown unexpectedly

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1866?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1866: --------------------------------- Labels: reported-by-qe verifier (was: reported-by-qe) > Verification reporting: Missing range is thrown unexpectedly > ------------------------------------------------------------ > > Key: DROOLS-1866 > URL: https://issues.jboss.org/browse/DROOLS-1866 > Project: Drools > Issue Type: Sub-task > Affects Versions: 7.0.0.Beta7 > Reporter: Jozef Marko > Assignee: Mario Fusco > Priority: Major > Labels: reported-by-qe, verifier > Fix For: 7.0.0.Final > > Attachments: Screenshot from 2017-03-22 14-42-47.png, Screenshot from 2017-03-22 14-43-08.png, Screenshot from 2017-03-22 14-56-59.png, redundancyAndConflicts.gdst, subsumptionAndMissingAction.gdst, subsumptionAndRedundancy.gdst > > > The attached guided decision table contain next to the expected verification messages also message about Missing range. These messages about Missing range are false positives and they shouldn't be present in the verification reporting. > To reproduce: > # Open the example *mortgages* project > # Navigate into the package: *mortgages.mortgages* > # Upload there all attached GDSTs: > ** subsumptionAndMissingAction.gdst > ** subsumptionAndRedundacy.gdst > ** redundancyAndConflicts.gdst > # Open subsumptionAndMissingAction.gdst and see the verification report > ** Subsumptant rows - correct > ** Rule has no action - correct > ** Missing range - *incorrect* > # Open subsumptionAndRedundancy.gdst and see the verification report > ** Subsumptant rows - correct > ** Redundant rows - correct > ** Missing range - *incorrect* > # Open redundancyAndConflicts.gdst and see the verification report > ** Conflicting rows - correct > ** Redundant rows - correct > ** Missing range - *incorrect* > Please unignore tests form PR https://github.com/kiegroup/drools-wb/pull/435 once the issue is fixed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1867) Verification reporting: Adapt reporting levels according to Hit Policy

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1867?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1867: --------------------------------- Labels: reported-by-qe verifier (was: reported-by-qe) > Verification reporting: Adapt reporting levels according to Hit Policy > ---------------------------------------------------------------------- > > Key: DROOLS-1867 > URL: https://issues.jboss.org/browse/DROOLS-1867 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta7 > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: reported-by-qe, verifier > > Reporting levels in the verification result's shouldn't be same for all hit policies. For example: Verification should detect redundancy and subsumption as errors for the Unique Hit Policy. Currently the verification detects these just as warnings for the Unique Hit Policy. > Please revise reporting levels used for different hit policies and ensure that the behavior of verification checks corresponds to the selected Hit Policy. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1864) Verification reporting: Missing Action hides Deficient Rows

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1864?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1864: --------------------------------- Labels: reported-by-qe verifier (was: reported-by-qe) > Verification reporting: Missing Action hides Deficient Rows > ----------------------------------------------------------- > > Key: DROOLS-1864 > URL: https://issues.jboss.org/browse/DROOLS-1864 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta7 > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: reported-by-qe, verifier > Attachments: Screenshot from 2017-03-21 16-52-08.png, deficientRowsAndMissingAction.gdst > > > The issue is that the Deficient rows message disappears, if the table contains Missing action issue. Compare the table from GUVNOR-2956 and the one attached in this jira. The table in this jira contains just one additional line in comparison with the table from GUVNOR-2956. The table from GUVNOR-2956 contains Deficient Rows messages so also the table from this jira should. > To reproduce the issue: > # Open the example mortgage project > # Navigate into package: mortgages.mortgages > # Upload the attached GDST > # See the validation results > ** There won't be Deficient rows > ** There should be Deficient rows -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1862) Verification reporting: Multiple verification issues affects each other

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1862?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-1862: --------------------------------- Labels: reported-by-qe verifier (was: reported-by-qe) > Verification reporting: Multiple verification issues affects each other > ----------------------------------------------------------------------- > > Key: DROOLS-1862 > URL: https://issues.jboss.org/browse/DROOLS-1862 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta7 > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: reported-by-qe, verifier > Attachments: reproducer.gdst > > > The decision table that contains different kinds of verification issues throws these issues in non deterministic way. It means that the table throws different set of issues if the table is opened multiple times. > The expected warnings: > ||Issue Type||Set of Rows|| > |Missing action|1| > |Subsumptant|2, 3| > |Redundant|4, 5| > |Conflict|6, 7| > |Deficient|8, 9| -- 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