question: testing about redux-saga HOT 5 CLOSED

@aft-luke I just created a PR (more like a discussion) about possibly similar issues with testing #45

from redux-saga.

How do I use a yielded value inside a generator to continue on with tests?

by calling next(mockResult).

 it('should wait for the next DO_SOMETHING', function() {
   sut.next().value.should.eql(io.take(actions.DO_SOMETHING))
 })

it('should dispatch a fetch request', function() {
  // inject mock result into next
  const mockThing = { thing: { id: 1 } }
  sut.next(mockThing).value.should.eql(io.fork(creators.fetchSomething)) 
  ....
}

If you want to simulate an error, call throw(mockResult) instead

Although you don't use it in the above example. We should provide a way to mock the result of forked tasks (e.g. fetch = in your example )

from redux-saga.

@yelouafi I was going to open another issue for a question very similar to this one, so I hope this is okay. Here is another case for testing

function* watchDoSomething() {
        while (true) {
            const response = yield io.take(actions.DO_SOMETHING)
            if(response.success) {
                 yield io.fork(fetchSomething())
            } else {
                // do something else
            }
        }
    }

How can I test that flow?

from redux-saga.

@josebalius This is related to #47. We need to provide an utility function to mock fork results

from redux-saga.

v0.6.0 includes a createMockTask function, see releases notes for usage example.

from redux-saga.