[chore] Add tests for network code propagation with consumererror #13424
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.
This adds some E2E tests that show how network codes propagate from the OTLP(/HTTP) exporter to the OTLP receiver (both serving over HTTP and gRPC). The goal is that as we add the new
consumererror.Errortype and any related types to the pipeline, we can use these tests to understand the net effect of the errors.Most of the tests won't require changes after we add the new error type, but note the comment in
TestHTTPToHTTPthat shows where the error type will add functionality.These tests don't cover a few things right now: