[JBoss JIRA] (DROOLS-2010) Add queries w/assign variables in "Expect" section of Test Scenario editor
by Klara Kufova (Jira)
[ https://issues.jboss.org/browse/DROOLS-2010?page=com.atlassian.jira.plugi... ]
Klara Kufova commented on DROOLS-2010:
--------------------------------------
[~danielezonca], is this still valid for Test Scenarios (Preview)?
> 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: Scenario Simulation and Testing, Test Scenarios Editor
> Affects Versions: 6.5.0.Final
> Environment: Tomcat 9 (CLI), Win7 x64, Google Chrome
> Reporter: Russell Morrisey
> Assignee: Toni Rikkola
> Priority: Major
>
> 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.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3021) [DMN Designer] Data Types - Constraints - Enumeration component
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3021?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3021:
---------------------------------------
Tester: Jozef Marko
> [DMN Designer] Data Types - Constraints - Enumeration component
> ---------------------------------------------------------------
>
> Key: DROOLS-3021
> URL: https://issues.jboss.org/browse/DROOLS-3021
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: future.png, prototype.png
>
>
> - When "Enumeration" is selected in the Constraints dialog, the following component must be loaded;
> !prototype.png|thumbnail!
> - The component contains a dynamic list to insert the possible values
> - The input is a simple input without any validation
> This component must be made considering that in the future, each kind of data will support a specific component (see the following example considering {{date}}):
> !future.png|thumbnail!
> ⚠️ This JIRA does not comprehends the widget that appears in the {{future.png}} file. This JIRA comprehends the only what appears in the {{prototype.png}} file.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-1719) Problems when defining a test scenario in Spanish with a Date field
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-1719?page=com.atlassian.jira.plugi... ]
Jozef Marko closed DROOLS-1719.
-------------------------------
Resolution: Rejected
This wont't be implemented due to newer version of Test Scenarios editor (Preview).
> Problems when defining a test scenario in Spanish with a Date field
> -------------------------------------------------------------------
>
> Key: DROOLS-1719
> URL: https://issues.jboss.org/browse/DROOLS-1719
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 6.5.0.Final
> Environment: KIE Workbench 6.5.0
> WildFly 1.10.x
> Reporter: R D
> Assignee: Toni Rikkola
> Priority: Minor
> Labels: drools-tools
> Attachments: MyTestEnglish_EnglishWorkbench.PNG, MyTestEnglish_SpanishWorkbench.PNG, MyTestSpanish_EnglishWorkbench.PNG, MyTestSpanish_SpanishWorkbench.PNG
>
>
> We detect two bugs:
> 1. When executing a test scenario in a KIE workbench in Spanish, a field defined as Date seems not to be parsed correctly and always enters the rule file as null.
> 2. When switching to English in the KIE workbench the test scenario we defined in Spanish does not load. When we change back to Spanish the page with the test scenario loads again.
> Why is this a bug?
> 1. When we create the same test scenario in a KIE workbench in English, the field defined as Date has a value in the rule file and this value is the one that is provided in the test scenario .
> 2. When we switch the KIE workbench to Spanish, the test scenario defined in English does not load.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-2029) [Test Scenario] Test ScenarioTestEditorServiceImpl runScenario method
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2029?page=com.atlassian.jira.plugi... ]
Jozef Marko closed DROOLS-2029.
-------------------------------
Resolution: Done
This wont't be implemented due to newer version of Test Scenarios editor (Preview).
> [Test Scenario] Test ScenarioTestEditorServiceImpl runScenario method
> ---------------------------------------------------------------------
>
> Key: DROOLS-2029
> URL: https://issues.jboss.org/browse/DROOLS-2029
> Project: Drools
> Issue Type: Task
> Components: Test Scenarios Editor
> Affects Versions: 7.2.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
> Attachments: 0001-GUVNOR-3447-Run-scenario-with-possible-transitive-im.patch
>
>
> The method runScenario of ScenarioTestEditorServiceImpl ensures that the Scenario uses correct imports during running. Most of tests tests just the method addDependentImportsToScenario that is internally used by runScenario method. Add more complex scenario that will use the method runScenario directly.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-1980) "EXPECT" Variable binding list is empty after saving/reloading test scenario
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-1980?page=com.atlassian.jira.plugi... ]
Jozef Marko closed DROOLS-1980.
-------------------------------
Resolution: Rejected
This wont't be implemented due to newer version of Test Scenarios editor (Preview).
> "EXPECT" Variable binding list is empty after saving/reloading test scenario
> ----------------------------------------------------------------------------
>
> Key: DROOLS-1980
> URL: https://issues.jboss.org/browse/DROOLS-1980
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 6.5.0.Final
> Environment: KIE workbench, Tomcat 9 (CLI), H2 database, Win7 x64, Google Chrome Version 57.0.2987.133 (64-bit)
> Reporter: Russell Morrisey
> Assignee: Toni Rikkola
> Priority: Major
> Attachments: kie wb bound var missing.png, kie wb bound var.png
>
>
> In the test scenario editor, when I save a test scenario where the "EXPECT" clause points to a bound variable, the bound variable does not load correctly when the scenario is re-opened from a save.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-2000) Test Scenario: Not possible to use a global
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2000?page=com.atlassian.jira.plugi... ]
Jozef Marko closed DROOLS-2000.
-------------------------------
Resolution: Done
This wont't be implemented due to newer version of Test Scenarios editor (Preview).
> 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
> Affects Versions: 7.7.0.Final
> Reporter: Toni Rikkola
> Assignee: Guilherme Carreiro
> 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.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-2018) Improved test features
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2018?page=com.atlassian.jira.plugi... ]
Jozef Marko closed DROOLS-2018.
-------------------------------
Resolution: Rejected
This wont't be implemented due to newer version of Test Scenarios editor (Preview).
> 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
> Priority: Major
>
> 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.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-1992) Test Scenarios: Simple setup gives OutOfMemoryError
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-1992?page=com.atlassian.jira.plugi... ]
Jozef Marko closed DROOLS-1992.
-------------------------------
Resolution: Rejected
This wont't be implemented due to newer version of Test Scenarios editor (Preview).
> 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.12.1#712002)
7 years, 6 months