Thanks for responding!

> So in order to test sagas, all you need is to run the generator and make sure it yields the things you expect it to yield.

This was the crux of what I found frustrating, actually. A simple saga with one or two steps was ok. Longer ones were painful. My test scripts ended up with these patterns:

- looking 80% like my application code

- needing to mock almost every step (every yield's output and input) - which bifurcates quickly if your sagas branch

- requiring digging into the emitted call/take/etc payloads (which seems the opposite of what you want when using a utility - I'd prefer to "let the utility just do its job" in the tests)

- brittle tests - when I changed a saga, I usually needed to change the test, rather than being able to leave the tests alone to prove my refactor works.

None of this put me off using redux-sagas. The benefits for the application code were worth it, IMO.