Thanks to both of you.
@David Idempotence (and functional style) will both mitigate the issue of
testing.
@Sharma #3 looks impressive and I hear the pain. Few questions:
* Since you already have the state machine modeling, can't the scheduler
actions also be modeled as a state machine
For our frameworks, we don't tend to do much automated testing of the Mesos
interface--instead, we construct the framework state, then send it a
message, since our callbacks take the state of the framework + the event
as the argument. This way, we don't need to have mesos running, and we can
trim
