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 🙏

© 2025 – Pkg Stats / Ryan Hefner

expect-to-enzyme

v0.0.1

Published

expect-to assertions for working with enzyme

Downloads

7

Readme

expect-to-enzyme

expect-to helpers for use with enzyme.

Installation

npm install --save-dev expect-to-enzyme

Import the assertions by name, or using a namespace

import { findOne, haveClass, haveProps } from 'expect-to-enzyme'

Assertions

  • findSome(selector, n) — takes a selector and asserts that it resolves to n nodes. Don't pass an n and the assertion will ensure that more than one node is matched. Also supports asserting off the matched node(s), see sub tests for details.

    Aliases:

    • findOne(selector)
    • findTwo(selector)
    • findThree(selector)
    const wrapper = shallow(
      <Foo className="test">
        <Bar />
      </Foo>
    )
    
    expect(wrapper).to(findOne(Bar)); // passes
    expect(wrapper).to(findTwo(Bar)); // expected to find 2...
  • haveClass(class) — assert that a node has a class

  • matchText(regex|string) - assert that a node's text includes some value,

  • equalComponent(<Node />) - assert that an enzyme matches another

  • haveProps(partialProps) - assert that a node has

  • haveEqualProps(props) - assert that a node all and only the props defined

  • haveExactProps(props) - assert that a node has props

  • haveProp(name) - asserts that a node has a prop. Also supports asserting off the props value, see sub tests for details.

  • assertEach(assertion) - Ensure that each node in a set matches an assertion

asserting found values

When an assertion works on a value inside of the original context, you can use the .and() method to write additional assertions on that value.

import expect from 'expect-to'
import { findOne } from 'expect-to-enzyme'

const View = ({ type, count }) =>
  <div>
    <input type="number" value={count} />
    <select value={type}>
      <option>html</option>
      <option>css</option>
      <option>js</option>
      <option>png</option>
    </select>
  </div>

describe('View', () => {
  it('renders count to an input of type number', () => {
    const wrapper = shallow(<View count={100} type="html" />)
    expect(wrapper).to(
      findOne('input')
        .and(haveProps({ type: 'number', value: 100 }))
    )
  })
})