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

Automate steps for e2e testing #112

Open
jdef opened this issue Apr 19, 2017 · 2 comments
Open

Automate steps for e2e testing #112

jdef opened this issue Apr 19, 2017 · 2 comments
Milestone

Comments

@jdef
Copy link
Contributor

jdef commented Apr 19, 2017

Via slack convo:

smoke tests:
(a) start up an etcd cluster; make sure that the number of expected servers is brought online
(b) kill a server, make sure that etcd-mesos brings it back online
(c) kill a node; make sure that etcd-mesos can cope with that (assuming that normal cluster size is >= 3 servers)
(d) bring the node back online; etcd should launch a server on it
(e) simulate intermittent network partitions between agent nodes running mesos and etcd server (e.g. by using ip tables to drop packets on mesos and etcd ports)
(f) while performing the server/node kills and/or network failures, have a process that continuously increments some counter value in etcd via its HTTP API, and then queries it and compares the result w/ was expected.

The universe package has an example of using an etcd-proxy to front access to the etcd cluster, probably makes testing (f) easier.

@pires
Copy link
Contributor

pires commented Apr 20, 2017

(e) and (f) seem a fit for some Jepsen integration.

@pires
Copy link
Contributor

pires commented Apr 21, 2017

Even though it's not Go, here's a project that one may leverage to implement e2e testing, Shakedown.

@pires pires added this to the backlog milestone Apr 22, 2017
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

2 participants