Break up the TestProject to individual projects per Resource/component

[joperezr]

trafficstars

Today, we have a single project which we use for several different component's tests which stands up several containers and services. As discussed offline, we want to break this project apart into individual ones per Resource, which will also allow us to add resource-specific tests to ensure things are working as expected. One example of resource-specific tests, would be to validate that resources that support volumes are working as expected.

@davidfowl has volunteered in taking a first stab at this and separate one resource project to see how it looks like, and we can then parallelize the effort from there.

Components:

• [x] Aspire.Hosting.Azure.Tests
• [x] Aspire.Hosting.Garnet.Tests
• [x] Aspire.Hosting.Kafka.Tests
• [x] Aspire.Hosting.MongoDB.Tests
• [x] Aspire.Hosting.MySql.Tests
• [x] Aspire.Hosting.Nats.Tests
• [x] Aspire.Hosting.NodeJs.Tests
• [ ] Aspire.Hosting.Oracle.Tests
• [x] Aspire.Hosting.Postgres.Tests
• [x] Aspire.Hosting.Python.Tests
• [x] Aspire.Hosting.Qdrant.Tests
• [x] Aspire.Hosting.RabbitMQ.Tests
• [x] Aspire.Hosting.Redis.Tests
• [x] Aspire.Hosting.SqlServer.Tests
• [x] Aspire.Hosting.Valkey.Tests
• [x] Aspire.Hosting.Elasticsearch.Tests
• [x] Aspire.Hosting.Keycloak.Tests
• [x] Aspire.Hosting.Milvus.Tests
• [ ] Aspire.Hosting.AWS.Tests
• [ ] Aspire.Hosting.Dapr

[radical]

It would be useful to add your name next to the item that you want to take, like Aspire.Hosting.Valkey.Tests (assigned: @radical).

[Alirexaa]

I'm currently working on Aspire.Hosting.MongoDB.Tests.

[eerhardt]

I'm currently working on Aspire.Hosting.MongoDB.Tests.

I added your name beside it.

Are you able to complete Extract Aspire.Hosting.Garnet.Tests project (dotnet/aspire#4871)?

[Alirexaa]

Are you able to complete Extract Aspire.Hosting.Garnet.Tests project (dotnet/aspire#4871)?

Yes, But I want to fix #4870 first.

[eerhardt]

Are you able to complete Extract Aspire.Hosting.Garnet.Tests project (dotnet/aspire#4871)?

Yes, But I want to fix #4870 first.

I don't think we should block the testing work on that. We can extract the existing tests, and add whatever functional tests work, without that issue being fixed. Then when the issue is fixed, it can add the appropriate tests at that time.

[Alirexaa]

I will work on Aspire.Hosting.SqlServer.Tests

[joperezr]

@sebastienros will follow up and skip the remaining tests, log an issue, and have this work complete.