[JBoss JIRA] (DROOLS-4769) Add an empty row on grid when importing "empty" csv
by Guilherme Gomes (Jira)
[ https://issues.redhat.com/browse/DROOLS-4769?page=com.atlassian.jira.plug... ]
Guilherme Gomes updated DROOLS-4769:
------------------------------------
Labels: drools-tools (was: )
> Add an empty row on grid when importing "empty" csv
> ---------------------------------------------------
>
> Key: DROOLS-4769
> URL: https://issues.redhat.com/browse/DROOLS-4769
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.30.0.Final
> Reporter: Anna Dupliak
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: drools-tools
> Attachments: DmnAssert.scesim, DmnAssert.scesim.csv, Driver Suspension Rules.dmn, image.png
>
>
> If user import csv file in DMN scenario, which contains only header, then the Background contains no rows see [^image.png]
> Steps to reproduce :
> # Import [^Driver Suspension Rules.dmn]
> # Import [^DmnAssert.scesim]
> # In scesim file import [^DmnAssert.scesim.csv]
> Expected: Grid with the cells state the same as after initialization
> Actual: user has no rows to add a value
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-2513) Add support for embedded test execution
by Guilherme Gomes (Jira)
[ https://issues.redhat.com/browse/DROOLS-2513?page=com.atlassian.jira.plug... ]
Guilherme Gomes updated DROOLS-2513:
------------------------------------
Labels: CustomerFocusTeam drools-tools (was: CustomerFocusTeam)
> Add support for embedded test execution
> ---------------------------------------
>
> Key: DROOLS-2513
> URL: https://issues.redhat.com/browse/DROOLS-2513
> Project: Drools
> Issue Type: Enhancement
> Components: dmn engine, Scenario Simulation and Testing
> Affects Versions: 7.7.0.Final
> Reporter: Edson Tirelli
> Assignee: Daniele Zonca
> Priority: Major
> Labels: CustomerFocusTeam, drools-tools
>
> TCK test cases can be embedded in the DMN model under the extension elements (e.g., see Trisotech generated models).
> Add a public API to allow execution of embedded test cases.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-2015) Add agenda group config to test scenarios
by Guilherme Gomes (Jira)
[ https://issues.redhat.com/browse/DROOLS-2015?page=com.atlassian.jira.plug... ]
Guilherme Gomes updated DROOLS-2015:
------------------------------------
Labels: drools-tools (was: )
> Add agenda group config to test scenarios
> -----------------------------------------
>
> Key: DROOLS-2015
> URL: https://issues.redhat.com/browse/DROOLS-2015
> Project: Drools
> Issue Type: Enhancement
> Components: Test Scenarios Editor
> Affects Versions: 7.0.0.Beta5
> Reporter: Jess Evans
> Priority: Major
> Labels: drools-tools
>
> 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.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-4729) Change Unexpected error on Error if DMN got invalidated
by Guilherme Gomes (Jira)
[ https://issues.redhat.com/browse/DROOLS-4729?page=com.atlassian.jira.plug... ]
Guilherme Gomes updated DROOLS-4729:
------------------------------------
Labels: CustomerFocus drools-tools (was: CustomerFocus)
> Change Unexpected error on Error if DMN got invalidated
> --------------------------------------------------------
>
> Key: DROOLS-4729
> URL: https://issues.redhat.com/browse/DROOLS-4729
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.29.0.Final
> Reporter: Anna Dupliak
> Assignee: Daniele Zonca
> Priority: Minor
> Labels: CustomerFocus, drools-tools
> Attachments: Traffic Violation Rules.dmn, image-2019-11-05-18-30-40-011.png, image-2019-11-05-18-31-30-232.png
>
>
> If user created DMN based scenario test and used a property from it and after some time that property disappeared - then if we reopen test scenario editor we got
> *Error as expected see*
> !image-2019-11-05-18-30-40-011.png|thumbnail!
> But if user wants to edit any of the value we got
> *Unexpected error*
> !image-2019-11-05-18-31-30-232.png|thumbnail!
> Steps to reproduce
> # Import DMN [^Traffic Violation Rules.dmn]
> # Create test scenario asset for this dmn and save
> # Go back to DMN and remove Driver Should the driver... DMN objects and save
> # Open test scenario
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-4636) Update Scenario Cheatsheet to mention MVEL and Background
by Guilherme Gomes (Jira)
[ https://issues.redhat.com/browse/DROOLS-4636?page=com.atlassian.jira.plug... ]
Guilherme Gomes updated DROOLS-4636:
------------------------------------
Labels: CustomerFocus drools-tools (was: CustomerFocus)
> Update Scenario Cheatsheet to mention MVEL and Background
> ---------------------------------------------------------
>
> Key: DROOLS-4636
> URL: https://issues.redhat.com/browse/DROOLS-4636
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Affects Versions: 7.27.0.Final
> Reporter: Anna Dupliak
> Assignee: Daniele Zonca
> Priority: Minor
> Labels: CustomerFocus, drools-tools
>
> Update Scenario Cheatsheet for MVEL expression usage.
> h3. Here are some topics that could be mentioned:
> Expressions for Rule based scenarios for simple types
> * Starts from "*#*"
> * Runs for +properties+
> * Runs for +duplicated+ properties
> * Returns the +same+ type as property type in *GIVEN*
> * Returns boolean in *EXPECTED*
> * Receives rule processed value as a *parameter* in *EXPECTED* via keyword "*actualValue*"
> * Applies java.util.Objects.equals(actualValue, expression result) on the expression result if the *EXPECTED* value not a *boolean*
> * Could run any of java function for the project
> * Exports and imports as any other value
> Limitations
> 1. Mvel expression results +not property same+ type - drives scenario +failure, error reason and highlighted+
> Use case:
> User inputs 1/2 to Integer property
> 2.Mvel execution throws +exception+ - drives scenario execution +stopping, failure, error alert+
> Use case:
> User inputs inexistent MVEL function in one of the properties
> 3.Mvel expression +exception stops+ expression +execution+ for all *EXPECT* colons
> Use case:
> User got one of the GIVEN fact expression excepted
> 4.Mvel +cannot be mixed+ with simple expressions in one cell
> Use case:
> For cell inputs :
> {code:java}
> [#4+4,68]
> #actualvalue>1
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months