You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why: Having interoperability tests with lots of transports, encryption mechanisms, and stream muxers is great. However, we need to stay backwards-compatible with legacy libp2p releases, with other libp2p implementations, and less advanced libp2p stacks.
Goal: Expand beyond unit tests and have expansive test-plan coverage that covers all protocols.
The content you are editing has changed. Please copy your edits and refresh the page.
p-shahi
changed the title
D. 🧪 Future-proof Testing (Expansive protocol test coverage)
Future-proof Testing (Expansive protocol test coverage) 🧪
Feb 1, 2023
eta: 2023Q3
Why: Having interoperability tests with lots of transports, encryption mechanisms, and stream muxers is great. However, we need to stay backwards-compatible with legacy libp2p releases, with other libp2p implementations, and less advanced libp2p stacks.
Goal: Expand beyond unit tests and have expansive test-plan coverage that covers all protocols.
Tasks
The text was updated successfully, but these errors were encountered: