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

active-enzyme

v3.0.1

Published

Boilerplate-free Enzyme testing

Downloads

15

Readme

active-enzyme Build Status

Boilerplate-free Enzyme testing.

Installation

$ npm install --save-dev active-enzyme

Enzyme is a great tool for performing tests on React components, especially using shallow rendering. This little library augments it with some niceties that allow you to easily lookup an element by className and save the resulting ShallowWrapper to a variable which is active--that is, it doesn't need to be requeried again after things change.

In a nutshell, a test such as this:

import React from 'react'
import { shallow } from 'enzyme'
import Greeting from './Greeting'

it('greets in multiple languages', () => {
  const name = 'John'

  const wrapper = shallow(<Greeting name={name} />)

  expect(wrapper.find('.greeting').text()).toBe(`Hello, ${name}!`)

  wrapper.find('.switchLanguage').simulate('click')
  expect(wrapper.find('.greeting').text()).toBe(`Bonjour, ${name}!`)

  wrapper.find('.switchLanguage').simulate('click')
  expect(wrapper.find('.greeting').text()).toBe(`Hello, ${name}!`)
})

can instead be written like this:

import React from 'react'
import { shallow } from 'active-enzyme'
import Greeting from './Greeting'

it('greets in multiple languages', () => {
  const name = 'John'

  const {
    greeting,
    switchLanguage
  } = shallow(<Greeting name={name} />).classes

  expect(greeting.text()).toBe(`Hello, ${name}!`)

  switchLanguage.simulate('click')
  expect(greeting.text()).toBe(`Bonjour, ${name}!`)

  switchLanguage.simulate('click')
  expect(greeting.text()).toBe(`Hello, ${name}!`)
})

The two main features at work here are:

  1. Enzyme wrapper objects acquire a special classes property which allows you to query based on a class names. This is nice because it allows you to use ES2015 destructuring syntax as above to select all the rendered elements you care about for a given test.
  2. The first feature wouldn't be very useful with regular Enzyme if your test triggers re-renders of the element tree (as is happening here implicitly as a result of the 'click' events), because the greeting and switchLanguage wrappers are normally immutable. This library instead returns active wrappers, which change in response to the element tree being re-rendered.

Since the most common usage pattern is that you have a bunch of tests all testing the same component, there is a makeRenderer() utility which allows the individual tests to simply vary the props they're going to render it with:

import { makeRenderer } from 'active-enzyme'
import Greeting from './Greeting'

const render = makeRenderer(Greeting)

it('greets in multiple languages', () => {
  const name = 'John'

  const { greeting, switchLanguage } = render({ name }).classes

  expect(greeting.text()).toBe(`Hello, ${name}!`)

  switchLanguage.simulate('click')
  expect(greeting.text()).toBe(`Bonjour, ${name}!`)

  switchLanguage.simulate('click')
  expect(greeting.text()).toBe(`Hello, ${name}!`)
})

This has the nice added bonus that you no longer need to import React in your test suites!