We have a number of integration tests that setup an instance of the bus in order to send messages to our endpoints under test. We've configured these bus instances to be send only with the expectation that they would not create an input queue (since they are send only). However, we are finding that they do create a queue. This results in our health monitoring tools sending alerts when they find queues that are inactive (not polled). For instance, here is how we construct a bus instance in the integration test:
var bus = Configure.With()
.DefaultBuilder()
.UseTransport(() => _AzureServiceBusConnectionStringForProd)
.UnicastBus()
.SendOnly();
After the test has run, we find that a new queue and topic have been created with the name of the assembly containing this code.
We have a number of integration tests that setup an instance of the bus in order to send messages to our endpoints under test. We've configured these bus instances to be send only with the expectation that they would not create an input queue (since they are send only). However, we are finding that they do create a queue. This results in our health monitoring tools sending alerts when they find queues that are inactive (not polled). For instance, here is how we construct a bus instance in the integration test:
var bus = Configure.With() .DefaultBuilder() .UseTransport(() => _AzureServiceBusConnectionStringForProd)
.UnicastBus()
.SendOnly();
After the test has run, we find that a new queue and topic have been created with the name of the assembly containing this code.