-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Integration Testing Spec #336
Comments
FYI, this is a good place to start for micro tests: https://github.com/libp2p/go-libp2p/tree/master/p2p/net/mock (although we should still have some form of DSL). |
@Stebalien Awesome, thanks. I did eventually wade my way into that folder. Maybe even just a configuration interpreter that creates networks based on that interface. |
Really, we could define those configurations using go datastructures instead of parsing a separate file. One can, e.g., write: net := Make(TestNet{
Nodes: []TestNode{
{
Name: "PeerA",
...
},
},
Links: []Link{
{
From: "PeerA",
To: "PeerB",
DefaultUp: true,
Latency: ...,
...
}
},
})
net.Link("PeerA").Down()
... |
Yep! That sounds perfect |
New home at protocol/research-grants#4 |
Opening a new issue to start a discussion around integration testing for go-libp2p.
In order to test more complex behaviors of libp2p, it's clear we'll want some sort of test harness in place. In my view, there are two tiers of this that could use doing:
I've got to run for now, but wanted to get this discussion started! I think both the micro and macro options are useful, so it's really just a matter of determining when we want to spec/implement.
@whyrusleeping @jbenet @mgoelzer
The text was updated successfully, but these errors were encountered: