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

react-context-inspector

v1.0.1

Published

Test react context with easy, good to combine with enzyme

Downloads

4

Readme

GitHub Workflow Status Code Climate maintainability Code Climate issues Code Climate technical debt

react-context-inspector

Tiny tool that helps you when testing your context in complex test scenarios. Compatible with react and react-native. Very helpful with Enzyme.js.

Install

npm install --save-dev react-context-inspector

API reference

createContextInspector

Returns TestComponent, that has chainable methods

import { createContextInspector } from 'react-context-inspector'
createContextInspector(YourContext)

.onMount

Trigger event on mount

import { createContextInspector } from 'react-context-inspector'
const TestComponent = createContextInspector(YourContext)
  .onMount(props => props.load('foo'))

.onRender

Trigger event on every render

import { createContextInspector } from 'react-context-inspector'
const TestComponent = createContextInspector(YourContext)
  .onRender(props => props.load('foo'))

.onFirstRender

Trigger event on first render

import { createContextInspector } from 'react-context-inspector'
const TestComponent = createContextInspector(YourContext)
  .onFirstRender(props => props.load('foo'))

.waitFor

Prevents from rendering children and triggering onRender and onFirst render. Very useful when testing asynchronous states

import { createContextInspector } from 'react-context-inspector'
const TestComponent = createContextInspector(YourContext)
  .waitFor(props => props.initialized)

.setChildren

Use this when you need to protect the tested content from rendering before somethigng happens. Usually combined with .waitFor

import { createContextInspector } from 'react-context-inspector'
const TestComponent = createContextInspector(YourContext)
  .setChildren(<MyComponent />)
  .waitFor(props => props.initialized)

Example usage

This example basically covers everything.

import React, {createContext} from 'react'
import { createContextInspector } from 'react-context-inspector'


describe('Test component', () => {
  it('provides user name', () => {
    const UserContext = createContext('User')
    function UserDetail () {
      const { name } = useContext(UserContext)
      return <div>{name}</div>
    }
    const TestComponent = createContextInspector(UserContext)
      .setChildren(<UserDetail />)
      .waitFor(({ name }) => name === 'Qui-Gon Jinn')
      .onMount(({ load }) => setTimeout(() => load('Qui-Gon Jinn')))
      .onFirstRender(({ afterLoad, name }) => afterLoad(name))
    const load = jest.fn()
    const afterLoad = jest.fn()
    function TestWrapper ({ name }) {
      return (
        <UserContext.Provider value={{ afterLoad, load, name }}>
          <TestComponent />
        </UserContext.Provider>
      )
    }
    const comp = mount(<TestWrapper name='Obi-Wan Kenobi' />)
    load.mockImplementation((name) => comp.setProps({ name }))
    // We need to wait because the test is entangled
    await new Promise(resolve => setTimeout(resolve))
    expect(load).toHaveBeenCalledWith('Qui-Gon Jinn')
    expect(afterLoad).toHaveBeenCalledWith('Qui-Gon Jinn')
    expect(comp.find(TestComponent.Inspector).props())
      .toHaveProperty('name', 'Qui-Gon Jinn')
  })
})