Explore options to host endpoints outside of the test agent process

[mauroservienti]

If each endpoint that participates in a test was in its container, and the testing infrastructure deploys the required set of behaviors, they could communicate and report back their staus to the test.

[mauroservienti]

Another option on the same path would be to:

• the integration scenario context creates a named pipe
• Endpoints will be “referenced” by tests only using the project path
• When the test starts it’ll use Process.Start to run the endpoints
• Each endpoint needs to be augmented with behaviors that will use named pipes, or StreamJsonRpc, to communicate back to the test agent

in this way the runtime doesn’t impact anymore and different endpoints could use different versions of NServiceBus. The named pipe could also be used to pilot endpoints by exposing basic Send/Publish options generally needed to kickoff tests.