Write containerized end-to-end tests

[connorkuehl]

It would be cool if we could bring up a server and n-clients with docker-compose or something. They can just run the client and server binaries in the examples/ folder.

Injecting network faults to cover things like timeouts and packet retransmissions would be awesome.

Ultimately, this might be something that could be incorporated into CI (once it exists...)

[lukeyeh]

Hey @connorkuehl would be up to take a look at this. Could you provide a couple more code pointers to get me up to speed?
Thanks!

[connorkuehl]

Hey @lukeyeh! That'd be great, thank you 🙂

This issue tends more towards infrastructure than anything else, so I don't think a whole lot of familiarity with the codebase is required outside of knowing:

• Docker and docker-compose (bonus if you can use these to inject faults)
• How to run the client and server example (this is detailed in the README)
• How to incorporate this into Travis CI .travis.yml

My friend @squidboylan is really good with this kind of thing, so I just wanted to loop him into the thread in case you had any questions. That's not to say that I won't be around, but three brains is definitely better than two!

This issue has a larger scope than many of the other issues I've been opening on this repo, so if it's something that you change your mind about just let me know and we can unassign the ticket.

[lukeyeh]

Cool! I have a general idea on how to get this up and running. I'll open a pull request some time this weekend!