Bug 988876

Summary: Test scenario cannot find facts from the same package
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: high Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: etirelli, lpetrovi, rrajasek
Target Milestone: ER4Keywords: TestBlocker
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 20:16:35 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:

Description Jiri Locker 2013-07-26 15:29:33 UTC
Description of problem:
It is impossible to run a test scenario if it is in a non-default package AND it uses facts from that package (i.e. no need to import them).

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

How reproducible:
easily

Steps to Reproduce:
1. use mortgages project in uf-playground
2. create a new object in a new package, e.g. my.cool.stuff.Something using Data modeler (don't forget to save it)
3. go to my.cool.stuff package and creat a new Test scenario
4. Insert Something, run test, check Reporting window

Actual results:
Unable to find class 'Something'.

Expected results:
The test should pass without errors.

Additional info:

Comment 2 Jiri Locker 2013-07-26 15:48:49 UTC
One more related thing -- when adding expectation, no rules are offered from the select box, but this doesn't depend on package name. It doesn't work for mortgages test scenarios too.

Comment 3 Jiri Locker 2013-08-23 14:58:17 UTC
(In reply to Jiri Locker from comment #2)
> One more related thing -- when adding expectation, no rules are offered from
> the select box, but this doesn't depend on package name. It doesn't work for
> mortgages test scenarios too.

This has already been fixed and verified in bug 996490.

Comment 7 Jiri Locker 2013-10-17 17:32:02 UTC
Fixed in ER4.