October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2007) [Test Scenario] Upgrade UI to gwt-bootstrap-3 components

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2007?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3464 to DROOLS-2007: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2007 (was: GUVNOR-3464) Workflow: GIT Pull Request workflow (was: classic default workflow) Issue Type: Enhancement (was: Epic) Epic Colour: (was: ghx-label-6) Component/s: Test Scenarios Editor (was: Test Scenarios) Epic Name: (was: Test Scenario UI upgrade) Epic Status: (was: To Do) Affects Version/s: 7.2.0.Final (was: 7.2.0.Final) > [Test Scenario] Upgrade UI to gwt-bootstrap-3 components > -------------------------------------------------------- > > Key: DROOLS-2007 > URL: https://issues.jboss.org/browse/DROOLS-2007 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Affects Versions: 7.2.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1997) Test Scenario: kiebase and kiesession settings are not persisted

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1997?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2397 to DROOLS-1997: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1997 (was: GUVNOR-2397) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Test Scenarios Editor (was: Test Scenarios) > Test Scenario: kiebase and kiesession settings are not persisted > ---------------------------------------------------------------- > > Key: DROOLS-1997 > URL: https://issues.jboss.org/browse/DROOLS-1997 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Environment: 6.4.x snapshot kie-wb > Reporter: Zuzka Krejčová > Assignee: Toni Rikkola > Labels: qe-recommend-fix-before-6_4_Final, reported-by-qe > Attachments: test_scenario.webm > > > It is (in theory) possible to set the kie base/session in a test scenario. The dropdowns work. When you save the test scenario with this change and reopen it, the kie base/session reverts to the default. If you change the kie base and kie session and run the test scenario, the settings revert as well, this time also adding duplicates of the options into the dropdown. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1998) Guvnor Test Scenarios - "unable to find constructor" error using a Java Interface in the Facts model

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1998?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1289 to DROOLS-1998: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1998 (was: GUVNOR-1289) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Test Scenarios Editor (was: Test Scenarios) Affects Version/s: 5.5.0.Final (was: drools-5.1) > Guvnor Test Scenarios - "unable to find constructor" error using a Java Interface in the Facts model > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-1998 > URL: https://issues.jboss.org/browse/DROOLS-1998 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 5.5.0.Final > Environment: Mac OS X version 10.5.8, jboss 4.2.3, jdk_1.6 > Reporter: Alessandra Magenta > Assignee: Toni Rikkola > Labels: Test > Attachments: Sales.java, SalesImpl.java, repository_export.xml > > > If I use some Facts with a Java Interface I have an error on running Test Scenarios like: > There was an error executing the consequence of rule [SalesRule] > rule: SalesRule CAUSED BY [Error: unable to find constructor: Sales()] [Near : {... Unknown ....}] ^ [Line: 1, Column: 0] > I have a Java class SalesImpl that implement the Sale Interface > How I can resolve this error? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1999) Error: "write size larger than buffer can fit" when running test scenario in workbench

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1999?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3139 to DROOLS-1999: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1999 (was: GUVNOR-3139) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Test Scenarios Editor (was: Test Scenarios) > Error: "write size larger than buffer can fit" when running test scenario in workbench > -------------------------------------------------------------------------------------- > > Key: DROOLS-1999 > URL: https://issues.jboss.org/browse/DROOLS-1999 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Environment: KIE Drools Workbench - Distribution Wars-Version: 6.5.0.Final > Apache Tomcat 9.0 (CLI startup), Windows 7 x64 > H2 database > Reporter: Russell Morrisey > Assignee: Toni Rikkola > Attachments: KIE WB write size error.png, KIE test scenario.png > > > When I run a test scenario in the KIE Workbench, the test scenario completes normally, but after it's completed, I get a pop-up error dialog: > _Unable to complete your request. The following exception occurred: write size larger than buffer can fit._ > This looks like it may(?) be related to: > https://issues.jboss.org/browse/RHBPMS-1475 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2000) Test Scenario: Not possible to use a global

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2000?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2756 to DROOLS-2000: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2000 (was: GUVNOR-2756) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Test Scenarios Editor (was: Test Scenarios) > Test Scenario: Not possible to use a global > ------------------------------------------- > > Key: DROOLS-2000 > URL: https://issues.jboss.org/browse/DROOLS-2000 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Priority: Blocker > > Tried with two globals. One added into a DRL file and another added with menu New->Global Variable(s). > Neither of these two show up in the Test Scenario popup. Tried a full build, reopening the test scenario and even restarting the workbench. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2001) Can't enter time of day portion of Date object belonging to a fact in test Scenarios

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2001?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1577 to DROOLS-2001: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2001 (was: GUVNOR-1577) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Test Scenarios Editor (was: Test Scenarios) Affects Version/s: 5.5.0.Final (was: drools-5.1) Fix Version/s: 7.5.0.Final (was: 7.5.0.Final) > Can't enter time of day portion of Date object belonging to a fact in test Scenarios > ------------------------------------------------------------------------------------- > > Key: DROOLS-2001 > URL: https://issues.jboss.org/browse/DROOLS-2001 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 5.5.0.Final > Environment: Running on Windows 7 with BRMS Standalone 5.1. Issue arises in both firefox and google chrome browsers. > Reporter: Jeff Forte > Assignee: Guilherme Carreiro > Fix For: 7.5.0.Final > > > I have a set of facts that hold a Date asset for comparison between each other. The comparison is supposed to be between the time of day of the object; however, when trying to enter the date and time of day into the test scenario the time of day portion always gets wiped upon running the scenario. The date stays but there is no long any time of day and I can't seem to find a way to enter the time even with the "enter date" button. I can't test while this is happening. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1990) Test Scenarios: Editor not allowing selection from variable for field value, then corrupts value that I entered as literal after successful test run

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1990?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1152 to DROOLS-1990: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1990 (was: GUVNOR-1152) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Test Scenarios Editor (was: Test Scenarios) Affects Version/s: 5.5.0.Final (was: drools-5.1) > Test Scenarios: Editor not allowing selection from variable for field value, then corrupts value that I entered as literal after successful test run > ---------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1990 > URL: https://issues.jboss.org/browse/DROOLS-1990 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 5.5.0.Final > Environment: Guvnor running under Tomcat (7, I think) on Windows XP dual core. Guvnor accessed via Firefox 3.x. > Reporter: Chris Clark > Assignee: Toni Rikkola > > I have an object mode written in Java and imported as a JAR file. The model contains the following (actual class names changed for clarity): > interface FlyweightIndicator > { > String getCode(); > void setCode(String); // I'd prefer not to have this, but needed it for setting up my test case > } > abstract class AbstractFlyweightIndicator implements FlyweightIndicator > { > String code; > // basic implementations for get/set Code > } > class ConcreteFlyweight extends AbstractFlyweightIndicator > { > ConcreteFlyweight() > { > code = "Something"; > } > } > class ReferencingClass > { > private FlyweightIndicator myInd; > // standard implementations for get/set myInd > // some other properties, some primitives, mostly Objects > } > I have a rule which which is supposed to fire when there is a ReferecingClass that has myInd set to a specific flyweight object. > When I went to code the test case, I created a GIVEN instance of the ConcreteFlyweightClass [$fly] (and had to set the code, the constructor didn't seem to get called to set it?). > Then I created another GIVEN for the ReferencingClass [$ref]. I added the myInd field. > Problem #1 > Is that the editor won't give me the option to bind $fly to the field. I only get a text box. > So I typed in "=$fly". > The test case ran and it passed. Typing in $fly seems to have done what I wanted and set the variable. > Problem #2 > Is that after the one successful run, the GIVEN section changed the myInd field to a dropdown, but it didn't include $fly as the value. When I clicked on the arrow beside the dropdown, $fly wasn't listed. So the field is now not set properly and the rule will fail with a null warning. > I could live with having to type =$fly into the text box, although it should ideally allow me to bind to the variable. But having that removed and replaced with an empty dropdown makes the text case unusable. :( -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1991?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1850 to DROOLS-1991: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1991 (was: GUVNOR-1850) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Test Scenarios Editor (was: Test Scenarios) > 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 > > 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.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1992) Test Scenarios: Simple setup gives OutOfMemoryError

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1992?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2720 to DROOLS-1992: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1992 (was: GUVNOR-2720) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Test Scenarios Editor (was: Test Scenarios) > Test Scenarios: Simple setup gives OutOfMemoryError > --------------------------------------------------- > > Key: DROOLS-1992 > URL: https://issues.jboss.org/browse/DROOLS-1992 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Priority: Minor > > The problem is the rule fires 10 000 times. I left no-loop out for that rule. 10 000 is the maximum amount of rules that can fire by default when running test scenarios. > This issue is now reported with the default workbench error popup, but it should be captured by the Test Scenario runner. Meaning, instead of failing the workbench, it should just fail the scenario test. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1993) Test Scenarios: Boolean dropdown does not set the default value, even when it is shown for the user

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1993?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1663 to DROOLS-1993: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1993 (was: GUVNOR-1663) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Test Scenarios Editor (was: Test Scenarios) > Test Scenarios: Boolean dropdown does not set the default value, even when it is shown for the user > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-1993 > URL: https://issues.jboss.org/browse/DROOLS-1993 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Critical > > # Open "Are they old enough" > # Add new expect for 'application'. "true" is selected in the dropdown > # Run the scenario. Log shows that "" was compared instead of "true" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 October 2017