Currently, all requests in unit tests are routed to App Fabric by default. We should add the ability to discover services in AppFabricTestBase, so services can be discovered and requests can be sent to them. Useful for testing, especially in the context of namespaces.
Release Notes
None
Activity
Show:
Bhooshan Mogal July 23, 2015 at 1:52 AM
We do not do service discovery in unit tests. The recommended way is documented in the first comment on this bug. We can add this functionality if the need arises in future.
Ali Anwar May 21, 2015 at 5:40 AM
In unit tests, usually the handlers are interacted with directly, and services don't bind to a particular port, so can not be discovered. Wouldn't a better way just be to inject an instance of the handler you want, and use it directly? Maybe with a client, if needed?
Won't Fix
Pinned fields
Click on the next to a field label to start pinning.
Currently, all requests in unit tests are routed to App Fabric by default. We should add the ability to discover services in AppFabricTestBase, so services can be discovered and requests can be sent to them. Useful for testing, especially in the context of namespaces.