-
Notifications
You must be signed in to change notification settings - Fork 772
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
Try asp.net core tests with inproc server #3394
Merged
cijothomas
merged 5 commits into
open-telemetry:main
from
cijothomas:cijothomas/aspnetcoreinproc
Jun 22, 2022
Merged
Try asp.net core tests with inproc server #3394
cijothomas
merged 5 commits into
open-telemetry:main
from
cijothomas:cijothomas/aspnetcoreinproc
Jun 22, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
reyang
reviewed
Jun 20, 2022
test/OpenTelemetry.Instrumentation.AspNetCore.Tests/InProcServerTests.cs
Outdated
Show resolved
Hide resolved
reyang
approved these changes
Jun 20, 2022
Codecov Report
@@ Coverage Diff @@
## main #3394 +/- ##
=======================================
Coverage 85.96% 85.96%
=======================================
Files 271 271
Lines 9522 9522
=======================================
Hits 8186 8186
Misses 1336 1336
|
reyang
reviewed
Jun 22, 2022
test/OpenTelemetry.Instrumentation.AspNetCore.Tests/InProcServerTests.cs
Show resolved
Hide resolved
…erTests.cs Co-authored-by: Reiley Yang <reyang@microsoft.com>
cijothomas
commented
Jun 22, 2022
test/OpenTelemetry.Instrumentation.AspNetCore.Tests/InProcServerTests.cs
Outdated
Show resolved
Hide resolved
alanwest
reviewed
Jun 22, 2022
test/OpenTelemetry.Instrumentation.AspNetCore.Tests/InProcServerTests.cs
Show resolved
Hide resolved
alanwest
approved these changes
Jun 22, 2022
alanwest
added a commit
that referenced
this pull request
Jun 27, 2022
* Added Jaeger Propagator to Opentelemetry.Extensions.Propagators (#3309) * Remove unnecessary bullet in CHANGELOG.md (#3352) Co-authored-by: Cijo Thomas <cithomas@microsoft.com> * Fix OTLP test (#3357) * Show that test is not doing what you might think it does * More asserts the merrier * Show this little test that it has potential * improve test coverage: InMemoryExporter & IDeferredMeterProviderBuilder (#3345) * [SDK] Circular buffer tweaks + cpu pressure test (#3349) * CircularBuffer tweaks and cpu pressure test. * Switch to Volatile.Read. * Perf tweaks. * Remove race check in debug after doing more testing. Co-authored-by: Cijo Thomas <cithomas@microsoft.com> * Fix event name logic + support null categoryname. (#3359) * In-memory Exporter: Buffer log scopes (#3360) * Buffer log scopes when using in-memory exporter. * CHANGELOG update. * Code review. * Tests. * CHANGELOG tweak. * SDK: Forward SetParentProvider to children of CompositeProcessor (#3368) * Examples: Fix ParentProvider not being set on MyFilteringProcessor (#3370) * Fix ParentProvider not being set on MyFilteringProcessor example. * Added XML comments. * Tweak. * Typo. * Logs: Add helper ctors & forceflush on OpenTelemetryLoggerProvider (#3364) * Add helper ctors & forceflush on OpenTelemetryLoggerProvider. * CHANGELOG update. * Unit tests. * Code review. * Code review. * Tweak. * SDK: Nullable annotations for base classes & batch + shims to enable compiler features (#3374) * Nullable annotations and shims for SDK base classes & batch. * Target updates. * Remove System.Collections.Immutable ref. * ApiCompat attribute exclusions. * ASPNETCore instrumentation to populate httpflavor tag (#3372) * improve test coverage: InMemoryExporter SnapshotMetric (#3344) * Fix AspNetCore metrics to use correct value for http.flavor (#3379) * Fix AspNetCore metrics to use correct value for http.flavor * word better * Logs: Add LogRecordData (#3378) * Add LogRecordData and hook up to LogRecord. * CHANGELOG update. * Code review. * Remove SetHttpFlavor from Http instrumentations (#3381) * Asp.Net Core trace instrumentation to populate http schema tag (#3392) * Try asp.net core tests with inproc server (#3394) * Dedupe IsPackable (#3398) * Remove AspNet and AspNet.TelemetryHttpModule instrumentation projects (#3397) * Handle possible exception when initializing the default service name (#3405) * HttpClient: Invoke Enrich when SocketException = HostNotFound (#3407) * Add & use ConfigureResource API. (#3307) Co-authored-by: tyler jago <ty_bone11@hotmail.com> Co-authored-by: Robert Pająk <rpajak@splunk.com> Co-authored-by: Cijo Thomas <cithomas@microsoft.com> Co-authored-by: Timothy Mothra <tilee@microsoft.com> Co-authored-by: Mikel Blanchard <mblanchard@macrosssoftware.com> Co-authored-by: Reiley Yang <reyang@microsoft.com> Co-authored-by: Utkarsh Umesan Pillai <utpilla@microsoft.com> Co-authored-by: Christian Neumüller <christian.neumueller@dynatrace.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current asp.net core tests are based on the "Test Server" concept. This PR attempts to use a in-proc asp.net core server.
For testing certain aspects like http/3, (eg: #3372), we might need to have a proper asp.net core server.
This is just an exploration of feasibility. No actual tests are moved. Need to evaluate this further, before using this as a the main test technique. Quite likely, we can use this only for very specific scenarios. The W3CIntegrationtests is already using this approach.