Add identify protocol to test-plans
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 65
- Forks
- 82
- PR merge metrics
- No merged PRs in 30d
Description
_Ideally our Testground tests would catch issues like this in the future. Given that our current Testground tests run the libp2p-ping protocol only, they have not caught it._
See: https://github.com/libp2p/rust-libp2p/issues/3244
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 the existing Testground test plan that runs the libp2p-ping protocol and compare its structure with the identify protocol requirement in libp2p/rust-libp2p#3244. Trace how protocols are selected and run, then confirm that the test plan exercises identify interoperability and catches the referenced issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100