Skip to content

Fix flaky test: use resilient HttpClient in YarpFunctionalTests #14920

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.

Sign up for GitHub

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

Merged
radical merged 1 commit into from
Mar 3, 2026
Merged

Fix flaky test: use resilient HttpClient in YarpFunctionalTests #14920

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions tests/Aspire.Hosting.Yarp.Tests/YarpFunctionalTests.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@
// The .NET Foundation licenses this file to you under the MIT license.

using Aspire.Hosting.ApplicationModel;
using Aspire.Hosting.Testing;
using Aspire.Hosting.Utils;
using Aspire.Hosting.Yarp.Transforms;
using Aspire.TestUtilities;
Expand Down Expand Up @@ -48,8 +49,7 @@ private async Task VerifyYarpResource(Action<IResourceBuilder<YarpResource>, End
await app.ResourceNotifications.WaitForResourceHealthyAsync(backend.Resource.Name, cts.Token);
await app.ResourceNotifications.WaitForResourceHealthyAsync(yarp.Resource.Name, cts.Token);

var endpoint = yarp.Resource.GetEndpoint("http");
var httpClient = new HttpClient() { BaseAddress = new Uri(endpoint.Url) };
using var httpClient = app.CreateHttpClient(yarp.Resource.Name);

using var response200 = await httpClient.GetAsync("/aspnetapp");
Assert.Equal(System.Net.HttpStatusCode.OK, response200.StatusCode);
Expand Down
Loading