And the error is coming from HipTest, so I assume that there's something that needs to be done in HipTest. If I remember the demo that I saw at Connect, I think there needs to be a test run configured in hiptest so the scenario execution can report back to that test run.
That's a good question. I guess, technically, it shouldn't. I wonder, though, if in the intialization of the execution engine, since they are all in the same suite, there isn't some attempt to make those connections no matter what project your automation is in. This is a question I think that would be worth addressing to support directly.