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-mock-element

v1.0.3

Published

mock element for capturing props in tests

Downloads

38

Readme

React mockElement

Mock element for capturing props in tests. Provides a middle-ground towards enzyme's shallow unit tests when using react-testing-library (but can be used with any testing library which renders to a DOM).

The intended use is to mock out specific children of a component under test which have important properties or are otherwise difficult to mock. This should not be used to mock every child component.

Install dependency

npm install --save-dev react-mock-element

Usage with react-testing-library + Jest

// code under test (MyComponent.jsx)

import React from 'react';

export default ({Child}) => {
  return (
    <div>
      foobar
      <Child p1="a" />
    </div>
  );
};


// test (MyComponent.test.jsx)

import React from 'react';
import {render, cleanup} from 'react-testing-library';
import mockElement from 'react-mock-element';
import MyComponent from './MyComponent';

describe('MyComponent', () => {
  it('creates a child element with a property', () => {
    const MyMockElement = mockElement('some-tag-name');

    const {container} = render(<MyComponent Child={MyMockElement} />);

    const child = container.querySelector('some-tag-name');
    expect(child.mockProps.p1).toEqual('a');
  });
});

afterEach(cleanup);

This is also compatible with Jest module mocking:

// code under test (MyComponent.jsx)

import React from 'react';
import ChildComponent from './ChildComponent';

export default () => {
  return (
    <div>
      foobar
      <ChildComponent p1="a" />
    </div>
  );
};


// test (MyComponent.test.jsx)

import React from 'react';
import {render, cleanup} from 'react-testing-library';
import mockElement from 'react-mock-element';
import MyComponent from './MyComponent';

jest.mock('./ChildComponent', () => mockElement('mock-child'));

describe('MyComponent', () => {
  it('creates a ChildComponent element with a property', () => {
    const {container} = render(<MyComponent />);

    const child = container.querySelector('mock-child');
    expect(child.mockProps.p1).toEqual('a');
  });
});

afterEach(cleanup);

API

mockElement(tagName): returns a React component which renders a tag with the given tag name (a naming convention such as mock-something is recommended but not required). Note that as this function name begins with mock, it can be used by hoisted jest.mock calls in tests (see second demo above).

element.mockProps: added to the HTMLElement prototype. This provides access to the props passed to an element. This is read-only.