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

@churchcommunitybuilder/redux-thunk-testing-library

v0.3.10

Published

Tools to test redux-thunk actions

Downloads

16

Readme

redux-thunk-testing-library

Tools to test redux-thunk actions

Installation

yarn add -D @churchcommunitybuilder/redux-thunk-testing-library

Usage

Without needing to extend the test runner class, you can use the exported expectThunk function

test('test', () => {
  return expectThunk(thunk())
    .toReturn(someValue)
    .run()
})

Note that .run() returns a promise, so you'll need to await it or return it

Mocks

withDispatch

Allows you to mock the dispatch function directly or provide mock return values

.withDispatch({
  args: [1],
  return true,
})

.withDispatch([
  {
    args: [1],
    return true,
  },
  {
    args: [2],
    return false,
  }
])

.withDispatch(dispatch => {
  dispatch.mockResolvedValue(true)
})

withActions

Allows you to provide actions that will be dispatched to the store, in order to mock state

.withActions(actionOne(), actionTwo())

Matchers

toDispatch

Asserts that the args were dispatched

.toDispatch(actionOne())

toDispatchActionLike

Asserts that the action creator was dispatched, regardless of the payload

.toDispatchActionLike(actionOne)

toReturn

Asserts that the thunk returned the given value

.toReturn(1)

toMeetExpectation

Asserts any custom expecation, and is called with the test runner context

.toMeetExpectation(({
  dispatch,
  getState,
  extraArg,
  output,
}) => {
  expect(getState()).toBe({})
})

Extending the ThunkTestRunner class

If you need more functionality than the base class grants, i.e. mocking/matchers around your thunk extra arg, you can extend the class and add public methods for your own use.

  class TestRunner extends ThunkTestRunner<ExtraArg> {
    toCallExtraArgWith(expectedValue: any) {
      return this.addExpectation(({ extraArg }) => {
        this.getExpectation(extraArg).toHaveBeenCalledWith(expectedValue)
      })
    }
  }

  const expectThunk = createExpectThunk(TestRunner, getStore, extraArg)