Jim Hall

Was this ever added?

This is a very important feature for me. Development is a real pain when I have to push every single change I make. Especially when debugging.

@axelson, I agree that `put` and `call` are the main items that should be tested. They are the items which have an effect on the application. `take` should be tested...

What I would like to see a sort of saga spy, which gives us the ability to write a test like this. ``` es6 let sagaSpy; beforeEach(() => { sagaSpy...

Spent a little more time on this approach with the goal of having this api. ``` es6 const spy = effectSpy(generator) .next('init') .next('getToken', token) // name and pass in yield...

I have been working on this [generator test runner](https://www.npmjs.com/package/generator-test-runner) for the past couple months that my team seems to enjoy for testing sagas/effects. I laid out the API [earlier in...

Whoops, spy, not promise. The selector detector could be any function, whatever makes the most sense! So long as it returns a bool. I would appreciate some advice on what...

I was having this issue as well. I had included a pyproject.toml file which I'm using to manage [black](https://github.com/psf/black). Serverless was looking at that file instead of requirements.txt. If you...

I removed that layout and where it was referenced, and that fixed it.

There will be some changes here and there. Feel free to open a PR, I will do my best to keep it up to date as changes come through