-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
[AzureMonitorDistro] add tests for aspnetcore instrumentation #44827
base: main
Are you sure you want to change the base?
Conversation
API change check API changes are not detected in this pull request. |
...etry.AspNetCore/tests/Azure.Monitor.AspNetCoreTestApp/Azure.Monitor.AspNetCoreTestApp.csproj
Show resolved
Hide resolved
...e.Monitor.OpenTelemetry.AspNetCore.Tests/Azure.Monitor.OpenTelemetry.AspNetCore.Tests.csproj
Show resolved
Hide resolved
...ests/Azure.Monitor.OpenTelemetry.AspNetCore.Tests/E2ETests/AspNetCoreInstrumentationTests.cs
Outdated
Show resolved
Hide resolved
? traceTelemetryItems.Any() | ||
: traceTelemetryItems.Any(predicate); | ||
}, | ||
timeout: TimeSpan.FromSeconds(20)); |
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.
Is there a reason for long time-out?
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.
Half the tests failed on the CI because no activity was exported.
I just increased the timeout in the last commit to see if they pass when given extra time.
Changes
Azure.Monitor.AspNetCoreTestApp
.This is using the AspNetCore Empty template.
This project will be used by unit tests to write a
WebApplicationFactory
-based test.AspNetCoreInstrumentationTests
.These tests verify that Request telemetry is created.