Red Hat Bugzilla – Bug 970786
Test scenario should support hierarchial object models and collections
Last modified: 2014-02-04 17:57:35 EST
Description of problem:
Test scenario doesn't support complex objects and collections
Version-Release number of selected component (if applicable):
Steps to Reproduce:
I'm using this model:
With a rule:
1) Add Fact, click on the Fact, choose "Multiple field constraint" : "Any of (Or)", click on "any of the following:" in the editor, choose subfact.
Then try clicking on that subfact to choose its field or bind a variable - it's not possible, not clickable.
2) Click the green plus sign to add a condition and choose "Any of the following are true", similarly to the above case, choose Fact, click it in the editor, but then choose "Add a restriction on a field" : subfact. Click on subfact in the editor.
You can either bind a variable to that fact or choose its field. BUT once you choose some field, subfact isn't clickable anymore. If you choose and insert a field before that, you can bind that to a variable too and once you bind it, it becomes unclickable too.
3) Save the rule, validate and verify - everything seems ok. Create a test scenario - you can't set the subfact.field inside a Fact.
subfact.field must accessible from test scenario
test scenario supporting complex objects
This issue was partially solved by Bug 724639, but test scenario was not fixed.