Skip to content

stats/opentelemetry: Write e2e tests for tracing more than single message sent and received #8240

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

Open
purnesh42H opened this issue Apr 10, 2025 · 1 comment · May be fixed by #8242
Open
Assignees
Labels
Area: Testing Includes tests and testing utilities that we have for unit and e2e tests within our repo. P2 Type: Testing

Comments

@purnesh42H
Copy link
Contributor

In all of the e2e tests, we only have single message being sent/received, which means that the logic on the sequence numbers incremented is untested. Write a separate test for streaming RPC where multiple messages are being sent and received and validate the traces accordingly

@purnesh42H purnesh42H added Area: Testing Includes tests and testing utilities that we have for unit and e2e tests within our repo. Type: Feature New features or improvements in behavior Type: Testing P2 and removed Type: Feature New features or improvements in behavior labels Apr 10, 2025
@vinothkumarr227
Copy link
Contributor

@purnesh42H Please assign the issue to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Testing Includes tests and testing utilities that we have for unit and e2e tests within our repo. P2 Type: Testing
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants