Jeremy Fairbank

Hi, @epikhighs. I initially introduced `withState` before `withReducer`, so that's part of the reason why they don't play nice together. I'm not opposed to changing the behavior, but I still...

Hi @hidalgofdz! The current problem is in how `expectSaga` works. It creates a saga function that sits between your real saga and redux-saga itself. Therefore, it can catch the error...

@hedgerh I believe this is JavaScript functioning as intended actually. If you run this code in Node or a browser, you'll get an uncaught exception. ```js function* saga() {} saga().throw(new...

Hi @KasperOlesen. In your first testing attempt, you don't seem to be using `expectSaga` or `dispatch` correctly. Since `applyMenu` accepts a `menuList` argument, you need to provide it in your...

Hi @rmevans9! Thanks for the suggestion. I think adding a helper to Redux Saga Test Plan to create mock tasks could be useful, considering it runs sagas with Redux Saga....

Great, thanks!

Stream of thought: This would require some rethinking of how providers work, possibly requiring a provider to be dropped after being consumed. That would need to be an opt-in behavior...

This isn't so much a bug as it is the way providers are defined. Providers aren't dropped after they match, so they will be continuously used if they match an...

Maybe the best approach would be another helper function in the `redux-saga-test-plan/providers` module. It could be called `times`, `limit`, or something to that effect. You could then compose that with...

Hi, @stinodes. I had put integration with a real store on hold because it would likely need some additional code in your main store creation to ensure redux-saga-test-plan can integrate...