Skip to content

Commit eef08f7

Browse files
committed
docs: add conformance fixture contribution guidance
1 parent 69dd57c commit eef08f7

1 file changed

Lines changed: 15 additions & 0 deletions

File tree

CONTRIBUTING.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -109,3 +109,18 @@ You may follow these steps to contribute:
109109
8. **Resolve any feedback.** Work with reviewers to address any comments or requested changes.
110110
111111
Be patient! It may take some time for your pull request to be reviewed and merged.
112+
113+
## Conformance fixture contributions (recommended pattern)
114+
115+
When proposing interoperability or conformance fixtures, include enough detail for
116+
maintainers and implementers to validate behavior consistently.
117+
118+
Suggested minimum metadata per fixture proposal:
119+
120+
- protocol area covered (for example: discovery, lifecycle, errors, streaming)
121+
- expected request/response shape or event sequence
122+
- pass/fail criteria that can be checked across SDKs
123+
- edge case rationale (why this fixture matters for interoperability)
124+
125+
For protocol-affecting fixture changes, link the related issue and document any
126+
specification assumptions directly in the PR description.

0 commit comments

Comments
 (0)