-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add management connection string API and tests #1519
Add management connection string API and tests #1519
Conversation
78161c8
to
881bedf
Compare
src/NServiceBus.Transport.RabbitMQ/Administration/ManagementClient/ManagementClient.cs
Outdated
Show resolved
Hide resolved
src/NServiceBus.Transport.RabbitMQ/Administration/ManagementClient/ManagementClient.cs
Outdated
Show resolved
Hide resolved
src/NServiceBus.Transport.RabbitMQ/Administration/ManagementClient/ManagementClient.cs
Outdated
Show resolved
Hide resolved
src/NServiceBus.Transport.RabbitMQ/Administration/ManagementClient/ManagementClient.cs
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding obsolete methods to a new major version feels a bit wrong to me, but I don't know the full context around the API mismatch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't really sure about this either. However, my thought process on this was that if users are still able to use the other obsolete methods for connectionString, I figured it would make sense to add the managementConnectionString method as well so it would be easier to integrate with their existing application and when the obsoletes are actually removed the migration to the updated API can all be done at once.
} | ||
|
||
[Test] | ||
public void Should_configure_broker_and_management_connection_configurations_with_single_connection_string() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since all the following tests are actually connecting to RabbitMQ, I'm wondering if they should be moved to the acceptance tests assembly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I wasn't 100% sure about this either. However, the RabbitMQContext.cs also connects to RabbitMQ, but it looks like only the tests that start with When_
are inheriting RabbitMQContext. which seem to all be acceptance tests, I think? However, they are still in the same Tests
project. I could separate them into a separate file that starts with When_
to indicate that they are acceptance tests. I don't know if that is a standard naming convention for acceptances tests, but it seems right.
No description provided.