transports/webrtc: Test `StreamMuxer` implementation with test harness
Open
Nobody has claimed this yet.
difficulty:moderate
getting-started
help wanted
priority:important
- Dominant language
- Rust
- Stars
- 5.6k
- Forks
- 1.3k
- Avg merge
- 8h 47m
- Merged PRs (30d)
- 19
Description
Description
We should be testing the new WebRTC transport StreamMuxer implementation with the (shiny) muxers/test-harness tests.
https://github.com/libp2p/rust-libp2p/tree/master/muxers/test-harness
Motivation
Make sure the behavior of our muxers is consistent.
Are you planning to do it yourself in a pull request?
No
Contributor guide
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 with the WebRTC transport's StreamMuxer implementation and the tests in muxers/test-harness. Run the harness against the implementation and compare its behavior with the existing muxer expectations. Done means the WebRTC StreamMuxer passes the harness tests and behaves consistently with the other muxers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100