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

fuzzprops

v0.0.1

Published

An experiment in automatically generating sets of supposedly-valid props for React components, in order to make tests write themselves.

Downloads

5

Readme

fuzzprops

An experiment in automatically generating sets of supposedly-valid props for React components, in order to make tests write themselves.

WARNING

This is experimental at best. React's maintainers are moving toward favoring Flow type-checking over propTypes. The algorithm for generating test props is quite slow. It's also pretty stupid and won't create much variation, which has both advantages and disadvantages.

That all said, except for slowing down your test suite, any shortcomings are mostly harmless.

How does it work?

It's a very simple, brute-force technique, like fuzzing is.

  • Start with a list of potential input values, which can be anything.
  • For each of a component's React.PropTypes validation functions, test every input value against it, keeping only the values that pass validation.
  • Use the lists of should-be-valid prop values to generate should-be-valid props objects.

You can then use those props objects to render the component and answer the question: "If I obey my PropTypes validation rules, does the component render without exploding?"

If your components explodes when given supposedly-valid props, you should consider either handling the input that made it explode or tightening its propTypes validation.

Usage

Mocha/enzyme/ES6 example:

import React, {Component, PropTypes, createElement} from 'react'
import {mount} from 'enzyme'
import fuzzProps from 'fuzzprops'

class Numbers extends Component {
  static propsTypes = {
    optionalNumber: PropTypes.number,
    requiredNumber: PropTypes.number.isRequired,
  };
  render() {
    return <div />
  }
}

const fuzzerValues = [
  'Hello, World!',
  null,
  undefined,
  -1,
  0,
  1,
  1234.4321,
  '1',
  '-1',
  '0',
  '1234.4321',
  {},
  [],
  [0],
  [0,0,0,0,0,0,0,0],
  ['1234', 2134, 'safasfa', null],
]

const maxIterations = 10

describe('Numbers component', function() {
  it('should render without throwing when given valid props', function() {
    fuzzProps(Numbers, fuzzerValues, maxIterations).forEach(function(props) {
      mount(<Numbers ...props>{props.children || null}</Numbers>)
    })
  })
})