October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2010) Add queries w/assign variables in "Expect" section of Test Scenario editor

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2010?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3149 to DROOLS-2010: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2010 (was: GUVNOR-3149) Workflow: GIT Pull Request workflow (was: classic default workflow) Issue Type: Enhancement (was: Feature Request) Component/s: Test Scenarios Editor (was: Test Scenarios) Affects Version/s: 6.5.0.Final (was: drools_6.5.0.Final) > Add queries w/assign variables in "Expect" section of Test Scenario editor > -------------------------------------------------------------------------- > > Key: DROOLS-2010 > URL: https://issues.jboss.org/browse/DROOLS-2010 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Affects Versions: 6.5.0.Final > Environment: Tomcat 9 (CLI), Win7 x64, Google Chrome > Reporter: Russell Morrisey > Assignee: Toni Rikkola > > In the Test Scenario editor, I want to be able to set up "Expect" clauses that chain together, like this: > {code:java} > $r1: A fact of type FieldValidation has values: > - fieldCode = "countryCode" > A fact of type FactAttributeValue has values: > - fieldValidation = $r1 > - type = "allowedValue" > - value = "US" > {code} > In this case, I want to query for the 1st object, store it in a variable, and use the variable value to verify the 2nd clause of the test. This is necessary to verify relationships between objects, such as master-detail relationships. It seems like the current Test Scenario editor interface does not support this. > The following rule snippet produces facts like those above, which seem untestable in the current Test Scenario editor: > {code:java} > when > ... > then > FieldValidation $r1 = new FieldValidation("countryCode") > insertLogical( $r1 ) > insertLogical( new FactAttributeValue($r1, "allowedValue", "US") ) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2012) QA: Add support for Events in tests (i.e. CEP)

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2012?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1458 to DROOLS-2012: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2012 (was: GUVNOR-1458) Workflow: GIT Pull Request workflow (was: classic default workflow) Issue Type: Enhancement (was: Feature Request) Component/s: Test Scenarios Editor (was: Test Scenarios) Affects Version/s: 5.5.0.Final (was: drools-5.2.0.CR1) > QA: Add support for Events in tests (i.e. CEP) > ---------------------------------------------- > > Key: DROOLS-2012 > URL: https://issues.jboss.org/browse/DROOLS-2012 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Affects Versions: 5.5.0.Final > Reporter: Michael Anstis > > Support for Complex Event Processing was added to Guvnor's authoring capabilities for 5.2. QA needs to support tests with Events and a pseudo-clock. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2011) Test scenarios: define a global variable which is org.apache.log4j.Logger, but add the global to test scenario .pop a message like 'Unable to run the scenario. org.apache.log4j.Logger' when I clicking test button

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2011?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1991 to DROOLS-2011: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2011 (was: GUVNOR-1991) Workflow: GIT Pull Request workflow (was: classic default workflow) Issue Type: Enhancement (was: Feature Request) Component/s: Test Scenarios Editor (was: Test Scenarios) > Test scenarios: define a global variable which is org.apache.log4j.Logger,but add the global to test scenario .pop a message like 'Unable to run the scenario. org.apache.log4j.Logger' when I clicking test button > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2011 > URL: https://issues.jboss.org/browse/DROOLS-2011 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Environment: > Reporter: 安耿 > Assignee: Toni Rikkola > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2013) BRM QA and automated rules testing

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2013?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1647 to DROOLS-2013: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2013 (was: GUVNOR-1647) Workflow: GIT Pull Request workflow (was: classic default workflow) Issue Type: Enhancement (was: Feature Request) Component/s: Test Scenarios Editor (was: Test Scenarios) Affects Version/s: 5.5.0.Final (was: drools-5.3.0.Beta1) > BRM QA and automated rules testing > ---------------------------------- > > Key: DROOLS-2013 > URL: https://issues.jboss.org/browse/DROOLS-2013 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Affects Versions: 5.5.0.Final > Environment: Mac OS X 5, JVM6, JBoss BRMS 5.1 > Reporter: Serge Emmanuel Pagop > Assignee: Toni Rikkola > > There is possible in BRM QA Tab in JBoss BRMS to create test scenarios. Will be great to give the possible to configure all these test scenarios to run automatically like in hudson or jenkins (e.g. in the midnight) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2014) Test Scenarios: It should be possible to check if the fields are empty, null or not null in the expect section

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2014?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1339 to DROOLS-2014: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2014 (was: GUVNOR-1339) Workflow: GIT Pull Request workflow (was: classic default workflow) Issue Type: Enhancement (was: Feature Request) Component/s: Test Scenarios Editor (was: Test Scenarios) > Test Scenarios: It should be possible to check if the fields are empty, null or not null in the expect section > -------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2014 > URL: https://issues.jboss.org/browse/DROOLS-2014 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2002) Test Scenario: (globals) should be in the expect section

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2002?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1659 to DROOLS-2002: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2002 (was: GUVNOR-1659) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Test Scenarios Editor (was: Test Scenarios) > Test Scenario: (globals) should be in the expect section > -------------------------------------------------------- > > Key: DROOLS-2002 > URL: https://issues.jboss.org/browse/DROOLS-2002 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Mark Coble > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2003) Test Scenarios: Leaving field value text boxes empty should be prohibitet for Numbers and similar

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2003?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1851 to DROOLS-2003: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2003 (was: GUVNOR-1851) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Test Scenarios Editor (was: Test Scenarios) > Test Scenarios: Leaving field value text boxes empty should be prohibitet for Numbers and similar > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-2003 > URL: https://issues.jboss.org/browse/DROOLS-2003 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Mark Coble > > null fields don't play well when the fields are populated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2004) Read only modes for editors

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2004?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1683 to DROOLS-2004: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2004 (was: GUVNOR-1683) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Enumerations Editor Test Scenarios Editor (was: Enumerations) (was: Test Scenarios) > Read only modes for editors > --------------------------- > > Key: DROOLS-2004 > URL: https://issues.jboss.org/browse/DROOLS-2004 > Project: Drools > Issue Type: Enhancement > Components: Enumerations Editor, Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Mark Coble > Priority: Minor > > There are more, best to check when work on this Jira starts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2005) Test Scenario: Call method should be in the Expect section

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2005?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1658 to DROOLS-2005: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2005 (was: GUVNOR-1658) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Test Scenarios Editor (was: Test Scenarios) > Test Scenario: Call method should be in the Expect section > ---------------------------------------------------------- > > Key: DROOLS-2005 > URL: https://issues.jboss.org/browse/DROOLS-2005 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Mark Coble > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2006) The audit log of test scenario is not easy to read. In version 5.x, it was easy

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2006?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2586 to DROOLS-2006: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2006 (was: GUVNOR-2586) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Test Scenarios Editor (was: Test Scenarios) Affects Version/s: 6.4.0.Final (was: drools_6.4.0.Final) > The audit log of test scenario is not easy to read. In version 5.x, it was easy > ------------------------------------------------------------------------------- > > Key: DROOLS-2006 > URL: https://issues.jboss.org/browse/DROOLS-2006 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Affects Versions: 6.4.0.Final > Reporter: Nicolas Heron > Assignee: Toni Rikkola > Labels: OnBoarding > Attachments: incorrectAuditLog.txt > > > In the text file attached is a log. > It should be more hiearchical -- 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