Hide Forgot
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.
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
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).
1045314 is now fixed and cherry-picked into 6.0.x
I have verified the fix is working for .rdrl and .gdst. I will wait for CR1 to check the rest of rule types.
Fix completed in CR1.