Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Future-proof Testing (Expansive protocol test coverage) 🧪 #64

Open
1 of 7 tasks
p-shahi opened this issue Oct 7, 2022 · 0 comments
Open
1 of 7 tasks

Future-proof Testing (Expansive protocol test coverage) 🧪 #64

p-shahi opened this issue Oct 7, 2022 · 0 comments

Comments

@p-shahi
Copy link
Member

p-shahi commented Oct 7, 2022

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

Preview Give feedback
  1. P0 effort/days kind/enhancement
    MarcoPolo
  2. mxinden
@p-shahi p-shahi transferred this issue from libp2p/go-libp2p Oct 20, 2022
@p-shahi p-shahi changed the title E. 🧪 Future-proof Testing D. 🧪 Future-proof Testing (Expansive protocol test coverage) Oct 20, 2022
@p-shahi p-shahi changed the title D. 🧪 Future-proof Testing (Expansive protocol test coverage) Future-proof Testing (Expansive protocol test coverage) 🧪 Feb 1, 2023
@p-shahi p-shahi pinned this issue Mar 23, 2023
@p-shahi p-shahi removed the starmaps label Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant