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-jest-util

v0.0.4

Published

A tool that assists in mocking of react components for use in jest

Downloads

12

Readme

Build Status

React Jest Utility Library

Testing react components in Jest can be a real pain at times. This library aims to add several utility functions that should make that process easier.

Installation

npm install --save-dev react-jest-util

If using the automocking feature of jest you should add 'node_modules/react-jest-util' to the unmockedModulePathPatterns list in your config.

API

mockComponent

This is similar to mockCompoent in the react test utilities but does a lot more. It will auto-mock all non-react functions in a component and restore props to the mock.

Accessing mocked functions

For convenience a reference to all the mocked methods of a component can be found as a key-value pair in mockedComponent.mockedMethods.

Signature

object ReactJestUtil.mockComponent(string modulePath [, string tagName = 'div' [, object methods]])

modulePath is the absolute path to the module, you can use require.resolve (or require.requireActual.resolve if in the context of jest) to obtain the absolute path from a relative path. tagName is an optional tag name that will be used for the mocked component, defaults to div. methods is an object of key-method pairs that will be attached to the created component. This will also overwrite any react added methods, such as render.

Complete Usage Example

var ReactJestUtil = require('react-jest-util');
var mockedComponentPath = require.resolve('../path/to/component');
var mockedComponent = ReactJestUtil.mockComponent(mockedComponentPath, 'Tag Name', {
    render: function() {
        return react.createElement(
            'MyTestTag',
            this.props,
            this.props.children
            );
        }
    });
console.log(mockedComponent.mockedMethods.foo.mock.calls); // assuming foo exists as a method on component

mockedComponent will contain a fully mocked React component that can be used in React Test Utilities renderIntoDocument.

log

Using console.log on React components can cause Jest to blowup because of too much ocntent being printed to stdout. This function uses node's util.inspect to print information about the object while keeping the amount of information printed low. It will also show information that otherwise would not be shown with console.log(obj).

Signature

ReactJestUtil.log(object obj [, integer depth = 0])

obj is the object to inspect and output and depth would be how deep to recurse into the object.

Usage

var myObj = {
    foo: {
        bar: 'foobar'
    }
}

ReactJestUtil.log(myObj, 1);
-> { foo: { bar: [Object] } }

License

React Jest Utility Library is released under the MIT license. See LICENSE.