Bug 1041303

Summary: Test scenario doesn't reflect changes in rules until the project is re-built
Product: [Retired] JBoss BRMS Platform 6 Reporter: Jiri Locker <jlocker>
Component: Business CentralAssignee: Toni Rikkola <trikkola>
Status: CLOSED CURRENTRELEASE QA Contact: Jiri Locker <jlocker>
Severity: urgent Docs Contact:
Priority: high    
Version: unspecifiedCC: etirelli, rzhang
Target Milestone: CR1   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1180074 (view as bug list) Environment:
Last Closed: 2014-08-06 20:18:53 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:
Bug Depends On:    
Bug Blocks: 1180074    

Description Jiri Locker 2013-12-12 14:22:21 UTC 
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.
Comment 1 Toni Rikkola 2013-12-16 13:50:58 UTC 
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
Comment 2 Jiri Locker 2014-01-10 13:33:23 UTC 
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).
Comment 3 Toni Rikkola 2014-01-10 14:23:59 UTC 
1045314 is now fixed and cherry-picked into 6.0.x
Comment 4 Jiri Locker 2014-01-10 14:35:45 UTC 
I have verified the fix is working for .rdrl and .gdst. I will wait for CR1 to check the rest of rule types.
Comment 5 Jiri Locker 2014-01-22 13:01:41 UTC 
Fix completed in CR1.