Defect: VirtResponse test steps have no visibility to their own test case, suite or sibling steps

You are right, unfortunately, now we don't have test step, test case or test suite items in Get Data for VirtResponse. We should add them in next releases.

But, actually, you can hand-write the property expansions in VirtResponse. You should use the new syntax we've introduced in 1.4 - the "full path" to properties, rather than references to current test suites, test cases etc. (which don't have much sense for Virt anyway). For example: ${#[TestSuite 1]#prop} or ${#[Yahoo Weather TestSuite#Virt TestCase#REST Request]#Response}. Look here for the details: http://readyapi.smartbear.com/features/expansions/syntax.

Ah yes, I agree with you on that, thanks for your clarification.

So looks like the underlying issue is that the VirtResponses are essentially getting their visibility from the parent Virt class, instead being given test step specific Get Data access.  The Get Data options in test Steps are the same as the options given in ServiceV Virt editors (plus they act weird when using them from test steps--e.g. Choosing Create New from the Virt option creates a property, but then there's noplace at all to see or manage the property for the VirstResponse step).