-
Notifications
You must be signed in to change notification settings - Fork 0
Add proto serialization round-trip tests #10
Copy link
Copy link
Open
Labels
area/protoProto definitions, message design, or wire compatibility work.Proto definitions, message design, or wire compatibility work.good first issueSmall, well-scoped tasks for new contributors.Small, well-scoped tasks for new contributors.help wantedLooking for community contributions.Looking for community contributions.kind/testsTesting, CI, or verification-only changes.Testing, CI, or verification-only changes.priority/lowNice-to-have or backlog item.Nice-to-have or backlog item.
Metadata
Metadata
Assignees
Labels
area/protoProto definitions, message design, or wire compatibility work.Proto definitions, message design, or wire compatibility work.good first issueSmall, well-scoped tasks for new contributors.Small, well-scoped tasks for new contributors.help wantedLooking for community contributions.Looking for community contributions.kind/testsTesting, CI, or verification-only changes.Testing, CI, or verification-only changes.priority/lowNice-to-have or backlog item.Nice-to-have or backlog item.
Problem statement
There are no tests that validate protobuf serialization/deserialization for the generated Go code. While the generated code is produced by well-tested protoc plugins, round-trip tests serve as regression guards for:
framewith audio/video/binary)FlowControl)google.protobuf.Structserialization with complex JSONProposed change
Add a new test file
gen/go/proto/transport/v1/proto_test.go(orproto_roundtrip_test.go):Affected area
Compatibility / migration
Test-only. No behavior change.
Additional context
Identified during QA review. These tests are particularly valuable before proto schema changes — they serve as the safety net that buf-breaking checks complement.