Test suites
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.8k
- Forks
- 320
- Avg merge
- 11d 15h
- Merged PRs (30d)
- 1
Description
Test suites should ideally use JSON for interoperability across virtually all languages.
Currently it appears that the test suites in https://github.com/libp2p/specs/blob/master/6-interfaces.md are in JS and Go.
There doesn't seem to be a suite/interface for NAT traversal and there isn't either for gossibsub, floodsub or multicast. Not sure off the top of my head what else is missing.
Additionally where using the same .proto protobuf file, this should make it easier for interoperability.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading 6-interfaces.md and inspecting the existing JavaScript and Go test suites described there. Inventory the missing NAT traversal, gossipsub, floodsub, and multicast suites, then clarify which JSON and shared protobuf interoperability requirements are in scope. Done should be a defined, agreed suite/interface plan with explicit coverage and compatibility criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, javascript, json
- Domain
- networking, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100