October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2015) Add agenda group config to test scenarios

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2015?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2931 to DROOLS-2015: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2015 (was: GUVNOR-2931) 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: 7.0.0.Beta5 (was: 7.0.0.Beta5) > Add agenda group config to test scenarios > ----------------------------------------- > > Key: DROOLS-2015 > URL: https://issues.jboss.org/browse/DROOLS-2015 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Affects Versions: 7.0.0.Beta5 > Reporter: Jess Evans > > I want to test rules within an agenda group. It would be helpful if test scenarios could preconfigure the agenda group stack. In other words, expose the equivalent of one or more KieCommands.newAgendaGroupSetFocus invocations to push groups onto the stack as a precondition (given) of the scenario. > Use of rule flow group, as an attempted workaround, causes the agenda rules to fire as desired, but the expectations do not match causing the scenario to fail even though the expected rules were fired and the expected facts asserted. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2016) In test scenario, when multiple instances of one class are created, to set a field value to null, instead of entering "=null", give the possibility to set "is null"

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2016?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1902 to DROOLS-2016: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2016 (was: GUVNOR-1902) 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.4.0.Final) > In test scenario, when multiple instances of one class are created, to set a field value to null, instead of entering "=null", give the possibility to set "is null" > -------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2016 > URL: https://issues.jboss.org/browse/DROOLS-2016 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Affects Versions: 5.5.0.Final > Reporter: Nicolas Heron > Attachments: Capture.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2017) Running Test Scenarios : Facility Needed to Output Results to File for Historical Reporting

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2017?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-40 to DROOLS-2017: ---------------------------------------------- Project: Drools (was: Guvnor) Key: DROOLS-2017 (was: GUVNOR-40) Workflow: GIT Pull Request workflow (was: classic default workflow) Issue Type: Enhancement (was: Feature Request) Component/s: Test Scenarios Editor (was: Test Scenarios) > Running Test Scenarios : Facility Needed to Output Results to File for Historical Reporting > ------------------------------------------------------------------------------------------- > > Key: DROOLS-2017 > URL: https://issues.jboss.org/browse/DROOLS-2017 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Environment: Mac OS X 10.5.5, Firefox 3.0.3 > Reporter: Ralph Jeffery > Assignee: Toni Rikkola > > When running Test Scenarios, a facility is required to output the results to a file. This is needed so that testing results can be retained as evidence of tests run. Taking screen shots from the browser is not a solution. > The output would need to show the version numbers of the Test Scenarios used and the Rules fired. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2018) Improved test features

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2018?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2613 to DROOLS-2018: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2018 (was: GUVNOR-2613) Workflow: GIT Pull Request workflow (was: classic default workflow) Issue Type: Enhancement (was: Feature Request) Component/s: Test Scenarios Editor (was: Test Scenarios) > Improved test features > ---------------------- > > Key: DROOLS-2018 > URL: https://issues.jboss.org/browse/DROOLS-2018 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Reporter: Toni Rikkola > > Covers the following: > * JUnit > * Test scenarios > * Simulation tests > * Cucumber > Everything above, expect the simulation tests use JUnit. At the moment the users can only run tests scenarios, but we should add support for any JUnit based tests. > In addition we should also put effort into making the reporting "pluggable" the JUnit gives an XML/text based report. When opening/showing the report we should show a more user friendly and visualized view. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2019) Test Scenario improvements

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2019?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1423 to DROOLS-2019: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2019 (was: GUVNOR-1423) Workflow: GIT Pull Request workflow (was: classic default workflow) Issue Type: Enhancement (was: Feature Request) Component/s: Test Scenarios Editor (was: Test Scenarios) > Test Scenario improvements > -------------------------- > > Key: DROOLS-2019 > URL: https://issues.jboss.org/browse/DROOLS-2019 > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2020) Test scenario should support hierarchial object models and collections and accumulates

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2020?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1416 to DROOLS-2020: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2020 (was: GUVNOR-1416) Workflow: GIT Pull Request workflow (was: classic default workflow) Issue Type: Enhancement (was: Feature Request) Component/s: Test Scenarios Editor (was: Test Scenarios) > Test scenario should support hierarchial object models and collections and accumulates > -------------------------------------------------------------------------------------- > > Key: DROOLS-2020 > URL: https://issues.jboss.org/browse/DROOLS-2020 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Reporter: Geoffrey De Smet > Assignee: Toni Rikkola > > "There is QA section on the BRMS where you can test rules. It supports only form the rule that has simple constraint with flat domain model. It doesn't support for hierarchical object model and rule collection, accumulation function as well." > should be part of the test scenario renaissance -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2021) Declarative Model Editor: Read only mode

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2021?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1684 to DROOLS-2021: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2021 (was: GUVNOR-1684) Workflow: GIT Pull Request workflow (was: classic default workflow) Fix Version/s: 5.5.0.Final (was: drools-5.3.0.Final) > Declarative Model Editor: Read only mode > ---------------------------------------- > > Key: DROOLS-2021 > URL: https://issues.jboss.org/browse/DROOLS-2021 > Project: Drools > Issue Type: Sub-task > Reporter: Toni Rikkola > Assignee: Michael Anstis > Priority: Minor > Fix For: 5.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2022) Decision Tables: View mode where editing is disabled

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2022?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1682 to DROOLS-2022: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2022 (was: GUVNOR-1682) Workflow: GIT Pull Request workflow (was: classic default workflow) Fix Version/s: 5.5.0.Final (was: drools-5.4.0.CR1) > Decision Tables: View mode where editing is disabled > ---------------------------------------------------- > > Key: DROOLS-2022 > URL: https://issues.jboss.org/browse/DROOLS-2022 > Project: Drools > Issue Type: Sub-task > Reporter: Toni Rikkola > Assignee: Michael Anstis > Priority: Minor > Fix For: 5.5.0.Final > > > Not a major issue. > * Open snapshots > * Open dtable from the snaptshots > * The editor allows editing > Saving changes is not possible because we are viewing a snapshot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2008) Test Scenarios: Ability to fail a Guvnor Test Scenario if any unexpected rules are fired when the test scenario is executed

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2008?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-531 to DROOLS-2008: ----------------------------------------------- Project: Drools (was: Guvnor) Key: DROOLS-2008 (was: GUVNOR-531) 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: Ability to fail a Guvnor Test Scenario if any unexpected rules are fired when the test scenario is executed > --------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2008 > URL: https://issues.jboss.org/browse/DROOLS-2008 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Reporter: Andrea Lee > Assignee: Toni Rikkola > Priority: Minor > > Example scenario: > Existing Rules: Rule A, Rule B, Rule C. > Test Scenario expectation: Expect Rule A to fire once. > I would like to have the ability to specify that this Test Scenario should fail if any other rule in addition to Rule A is fired WITHOUT having to specify the following additional expectations: Expect Rule B to not fire, Expect Rule C to not fire. > I have posted this in the user mailing list as well: http://n3.nabble.com/Guvnor-Test-Scenario-Expectations-td722429.html#a722429 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2009) Test Scenarios: Store the result history

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2009?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1744 to DROOLS-2009: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2009 (was: GUVNOR-1744) 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: Store the result history > ---------------------------------------- > > Key: DROOLS-2009 > URL: https://issues.jboss.org/browse/DROOLS-2009 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Reporter: Toni Rikkola > > Similar to what IntelliJ Idea has for java tests. > Would show a list of when the tests where ran and by who. Could also show the changes done to the rules that were used in the run. Mixture of version history and saved test scenario runs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 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