-
Notifications
You must be signed in to change notification settings - Fork 543
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
Extract Aspire.Hosting.Kafka.Tests project #4910
Conversation
Contributes to dotnet#3185 Contributes to dotnet#4294
@@ -306,25 +306,6 @@ public void EnsureAllRabbitMQManifestTypesHaveVersion0Suffix() | |||
Assert.Equal("container.v0", server.GetProperty("type").GetString()); | |||
} | |||
|
|||
[Fact] | |||
public void EnsureAllKafkaManifestTypesHaveVersion0Suffix() |
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 don't think this test adds value over the AddKafkaTests.VerifyManifest
test. That test verifies it is a container.v0 resource.
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.
ok :)
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.
Only thing that I notice is that you removed it from E2E tests, which is fine by me.
Yes, I think this is my recommendation going forward. Now that we have these "Functional" tests individually for each resource, I don't think we need the EndToEnd test to cover every individual resource. It just isn't scalable. Instead, I think we get the EndToEnd down to maybe ~5 core resources (a couple database, Redis, and maybe RabbitMQ) and the rest of these Hosting+Component tests are all in the functional tests. It makes the EndToEnd tests more maintainable. |
Contributes to #3185
Contributes to #4294
cc @Alirexaa
Microsoft Reviewers: Open in CodeFlow