npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@asaayers/redux-saga-tester

v0.1.1

Published

Test your sagas by intercepting effects

Downloads

5

Readme

@AsaAyers/redux-saga-tester

Project Status: Experimental

Expect every 0.x release to break the API. Nothing is settled.

I am releasing this under my namespace because 3LOK already has a redux-saga-tester. When the API settles and I want to release a 1.0.0, I'd like to have a different name.

Project Goals

  • Tests should not be tightly coupled to implementation
  • Tests should read in the same order as the saga
    • I think this makes them easier to read and understand

Example

For this example I created a toy saga based on 3LOK's comment.

function* addSaga() {
    const a = yield select(selectA)
    const b = yield select(selectB)

    const total = yield call(sum, a, b)

    yield put({
        type: "RESULT",
        payload: total
    })
}

I want to verify that this saga uses sum() to add store.a and store.b and updates store.result with the total. By default the tester doesn't tell you about yield select or yield put. they happen automatically.

import { addSaga, sum, reducer, selectResult, selectA, selectB } from "./add-saga.js"
test("add-saga", () => {
    const tester = SagaTester({
        initialState: {
            a: 2,
            b: 3,
        },
        reducer,
    })

    tester.testAgainst(addSaga, function* ({ getState }) {
        let actual

        // yield gives you the next effect from your saga that you want to test.
        // This didn't care about the selectors, they execute normally.
        actual = yield
        expect(actual).toEqual(call(sum, 2, 3))
        const callSumResult = 5

        // You need to yield a result back to the saga to continue and pick up
        // the next significant effect.
        actual = yield callSumResult
        // END is a special value automatically emitted when/if your saga ends
        expect(actual).toBe(END)

        // Instead of verifying the action was fired, now verify the state.
        actual = selectResult(getState())
        expect(actual).toBe(callSumResult)
    })
})

This test and some other variations are available in src/tests/add-saga.test.js.