[JBoss JIRA] (DROOLS-1820) Renaming a rule should update related test scenarios
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-1820?page=com.atlassian.jira.plugi... ]
Jozef Marko closed DROOLS-1820.
-------------------------------
Resolution: Rejected
This wont't be implemented due to newer version of Test Scenarios editor (Preview).
> Renaming a rule should update related test scenarios
> ----------------------------------------------------
>
> Key: DROOLS-1820
> URL: https://issues.jboss.org/browse/DROOLS-1820
> Project: Drools
> Issue Type: Enhancement
> Components: Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor, Impact Analysis
> Affects Versions: 5.5.0.Final
> Environment: JBoss BRMS 5.3.1 - Jboss EAP 6.1.1
> Reporter: Valentijn Scholten
> Priority: Major
> Labels: renaming, testscenario, user_experience
>
> Current behaviour:
> - Create a rule with name "test-rule".
> - Create a test scenario with an expect clause "test-rule" should fire at least once.
> - Populate the test scenario and test-rule in such a way that the test scenario runs succesfully with this expect clause.
> - Rename the rule from "test-rule" to "test-rule-renamed".
> - Run the test scenario again.
> - Observe the test scenario will fail because it expects a rule with name "test-rule" to be fired at least once. This rule no longer exists because it is renamed.
> Expected behaviour:
> - When the rule is renamed from "test-rule" to "test-rule-renamed", all test scenarios referring to this rule (in an expect clause or otherwise) should be updated transparently.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-534) Score Cards: Error in test scenario after update Guided Score Card
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-534?page=com.atlassian.jira.plugin... ]
Jozef Marko closed DROOLS-534.
------------------------------
Resolution: Rejected
This wont't be implemented due to newer version of Test Scenarios editor (Preview).
> Score Cards: Error in test scenario after update Guided Score Card
> ------------------------------------------------------------------
>
> Key: DROOLS-534
> URL: https://issues.jboss.org/browse/DROOLS-534
> Project: Drools
> Issue Type: Bug
> Components: Guided Score Card Editor, Test Scenarios Editor
> Reporter: Gennadiy Kruglov
> Assignee: Mark Proctor
> Priority: Major
> Labels: drools-tools
> Attachments: 2014-06-25_12-49-04.png, 2014-06-25_12-58-51.png
>
>
> In test scenario has error occurred after update Initial Score in Guided Score Card. There are the following error messages::
> 1) In the Reporting Pane - Unable to get a Session to run tests. Check the project for build errors.
> 2) In the Problems Pane - Found duplicate declaration for type ru.moneyman.rnd.rnd_moneyman_drools.Income
> Income – the field of declarative model class.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-1997) Test Scenario: kiebase and kiesession settings are not persisted
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-1997?page=com.atlassian.jira.plugi... ]
Jozef Marko closed DROOLS-1997.
-------------------------------
Resolution: Rejected
This wont't be implemented due to newer version of Test Scenarios editor (Preview).
> 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
> Priority: Major
> 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.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-689) Dependent Enumerations not working in Test Scenario, EXPECT section
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-689?page=com.atlassian.jira.plugin... ]
Jozef Marko closed DROOLS-689.
------------------------------
Resolution: Rejected
This wont't be implemented due to newer version of Test Scenarios editor (Preview).
> Dependent Enumerations not working in Test Scenario, EXPECT section
> -------------------------------------------------------------------
>
> Key: DROOLS-689
> URL: https://issues.jboss.org/browse/DROOLS-689
> Project: Drools
> Issue Type: Bug
> Components: Enumerations Editor, Test Scenarios Editor
> Affects Versions: 6.1.0.Final
> Reporter: Rares Vernica
> Assignee: Mark Proctor
> Priority: Major
>
> In Drools Workbench, I defined a dependent enumeration like:
> 'fact.f1' : ['a','b']
> 'fact.f2[f1=a]' : ['a1', 'a2']
> 'fact.f2[f1=b]' : ['b1', 'b2']
> The enumeration is detected properly and the drop-down box is displayed for Guided Rules and Test Scenario GIVEN section.
> The dependent filed is not detected properly for the Test Scenario EXPECT section and instead of the drop-down box a simple text box is displayed.
> If I populate the text box with a correct value from the enumeration, the scenario reports success, so the rule and the scenario is correct.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-691) Workflow Test Scenario error: org.foo.Bar cannot be cast to org.foo.Bar
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-691?page=com.atlassian.jira.plugin... ]
Jozef Marko closed DROOLS-691.
------------------------------
Resolution: Done
This wont't be implemented due to newer version of Test Scenarios editor (Preview).
> Workflow Test Scenario error: org.foo.Bar cannot be cast to org.foo.Bar
> -----------------------------------------------------------------------
>
> Key: DROOLS-691
> URL: https://issues.jboss.org/browse/DROOLS-691
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 6.1.0.Final
> Reporter: Rares Vernica
> Assignee: Toni Rikkola
> Priority: Major
>
> This is a bug with Workflow Test Scenario. I have two types:
> org.foo.Bar
> goz
> org.foo.Goz
> g1
> g2
> Bar has a member of type Goz called goz. Goz has two members g1 and g2 which have predefined values in an enumeration and g2 depends on the value of g1. I have a rule using them and the rule is fine.
> The problem is when I create a Test Scenario using them. The scenario has Goz and a Bar in the GIVEN section. Both are blinded to variable names and the goz member of Bar is initialized with the Goz instance.
> I first create Goz in the GIVEN section. I add g1 and g2 and assign literal values to them.
> Then I create Bar in the given section as well. Without any further changes I "Run scenario" and I get:
> Reporting:
> There were test failures
> Text
> Test : org.foo.Bar cannot be cast to org.foo.Bar
> It might be relate to DROOLS-689 which I reported earlier.
--
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:
---------------------------------------
Summary: [DMN Designer] Data Types - Constraints - Enumeration component (was: [DMN Designer] Data Types - Constraints - Enumeration option component)
> [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