`select` effect

Hi, I want to ask about handling select saga effect in tests.

My use case is: expectSaga(mySaga).withReducer(myReducer, initialReducerState)

In saga implementation I’m just calling const param = yield select((wholeState) => wholeState.moduleState.param)

So in result following code it is crushing because select effect is returning initialReducerState instead of wholeState.

Is it expected behaviour? Can it be handled without using fakes?

[olga-giza]

Yeah, to have my case covered, I used following mock:

expectSaga(mySaga)
...
.provide([
	[matchers.select.selector(selector), mockSelectorOutput]
])
...

Still I think that it is not so great to mock also the selectors so it would be cool to have that woking in the future.

[v-gachkovsky]

I have some trouble in unit test too. I have this test:

  testSaga(updateSetting, { payload: setting })
    .next()
    .call(putRequest, '/settings', setting)
    .next()
    .select(selectSettings())
    .next(settings)
    .put(updateSettingSuccess(settings));

And got an error on a string with ‘select’:

● updateSetting › encountered a declaration exception

    SagaTestError: 
    Assertion 3 failed: select effects do not match

    Expected
    --------
    { selector: 
       { [Function]
         resultFunc: [Function],
         recomputations: [Function],
         resetRecomputations: [Function] },
      args: [] }

    Actual
    ------
    { selector: 
       { [Function]
         resultFunc: [Function],
         recomputations: [Function],
         resetRecomputations: [Function] },
      args: [] }

My selector is:

import { createSelector } from 'reselect';
import { NAMESPACE } from './constants';
import { selectNamespace } from 'utils/reduxHelpers';

const selectSettings = () => createSelector(
  state => selectNamespace(state)(NAMESPACE),
  namespace => namespace.settings
);

How can I fix this issue?

“react”: “16.3.1”, “redux”: “3.6.0”, “redux-saga”: “0.15.3” “redux-saga-test-plan”: “^4.0.0-beta.1”,