Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1180074

Summary:	Test scenario doesn't reflect changes in rules until the project is re-built
Product:	[Retired] JBoss BRMS Platform 6	Reporter:	Zuzana Krejčová <zkrejcov>
Component:	Business Central	Assignee:	Toni Rikkola <trikkola>
Status:	CLOSED EOL	QA Contact:	Lukáš Petrovický <lpetrovi>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	6.1.0	CC:	alazarot, etirelli, jlocker, kverlaen, lpetrovi, rrajasek, rzhang, trikkola
Target Milestone:	ER5	Keywords:	Regression
Target Release:	6.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1041303	Environment:
Last Closed:	2020-03-27 19:42:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1041303
Bug Blocks:

Description Zuzana Krejčová 2015-01-08 09:55:43 UTC

+++ This bug was initially created as a clone of Bug #1041303 +++

Description of problem:
When test scenario is run it seems to use rules in the state when the project was last built. That means the test scenario ignores changes in rules *saved* by the user until project build is triggered and can be very confusing or mislead the user to believe that his changes in rules didn't break tests.

Version-Release number of selected component (if applicable):
ER5

How reproducible:
-

Steps to Reproduce:
1. go to mortgages
2. open Underage rule, change applicant age to 100, save the rule
3. open Are they old enough test scenario and run it (success is expected)
4. increase applicant age to 30 and run the test scenario

Actual results:
Test fails although the applicant age interval was increased to 100 and the application should be disapproved. If you build the project now and run the test again it will pass.

Expected results:
Test scenarios should always run with latest version of rules.

Additional info:
I think this may be caused by the change in triggering incremental build that also caused bug 1034785.

--- Additional comment from Toni Rikkola on 2013-12-16 14:50:58 CET ---

master:

https://github.com/droolsjbpm/guvnor/commit/1bb4819cc
https://github.com/droolsjbpm/drools-wb/commit/465f72ed4

6.0.x:

https://github.com/droolsjbpm/guvnor/commit/aa30de99a
https://github.com/droolsjbpm/drools-wb/commit/a9d129fe9

--- Additional comment from Jiri Locker on 2014-01-10 14:33:23 CET ---

I'm afraid the fix is incomplete because https://github.com/droolsjbpm/guvnor/commit/3f0e996170d50825f650fdf3e130ec0aa0f44c4e has not been cherry-picked to 6.0.x (and it cannot be as it contains changes related to bug 1045314).

--- Additional comment from Toni Rikkola on 2014-01-10 15:23:59 CET ---

1045314 is now fixed and cherry-picked into 6.0.x

--- Additional comment from Jiri Locker on 2014-01-10 15:35:45 CET ---

I have verified the fix is working for .rdrl and .gdst. I will wait for CR1 to check the rest of rule types.

--- Additional comment from Jiri Locker on 2014-01-22 14:01:41 CET ---

Fix completed in CR1.

Comment 3 Toni Rikkola 2015-01-21 10:18:27 UTC

Ok. There was no missing comment. Most likely the builder class changed and that broke the update for test scenarios. I added some unit tests to prevent this from happening in the future.

master
https://github.com/droolsjbpm/guvnor/commit/108f12517
https://github.com/droolsjbpm/kie-wb-common/commit/8afef1d43
https://github.com/droolsjbpm/drools-wb/commit/cb64b163a

6.2.x
https://github.com/droolsjbpm/guvnor/commit/23312ad2a
https://github.com/droolsjbpm/kie-wb-common/commit/2ffd921f0
https://github.com/droolsjbpm/drools-wb/commit/a8a6c6e38