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

selector-test-generator

v1.2.5

Published

Test generator for selectors based on reselect library

Downloads

15

Readme

Test generator for selectors based on reselect library.

Motivation

Writing unit-test for selectors based on reselect library depends on lot of boilerplate code. The sample selector test code looks like this

import state from <path_to_mocked_state>;
import { selector, anotherSelector } from <path_to_selector_folder>;

describe('Application/Selectors', () => {
  it('<selector>', () => {
    const received = selector(state);
    const expected = true;

    expect(received).toEqual(expected);
  });

  it('<anotherSelector>', () => {
    const received = anotherSelector(state);
    const expected = false;

    expect(received).toEqual(expected);
  });
});

The current pattern is repeated for most selectors, it takes a lot of time and demotivates writing simple unit tests, which can be quite a lot on a project.

selector-test-generator is trying to solve this problem by generating a file with jest tests for available selectors.

Using

This is a Node.js module available through the npm registry.

Installation is done using the npm install command:

npm install --save-dev selector-test-generator

or yarn add command:

yarn add --dev selector-test-generator

selector-test-generator ready to use as npm-script

selector-test-generator [selector-path-arg] [...options]

Also selector-test-generator run through npx without installing

npx selector-test-generator [selector-path-arg] [...options]

Options

  • selector-path-arg - define selector path in which the utility will search for selectors and generate tests. Optional argument, default value - current execution folder.
  • -s, --state <path> - set the mocked state location. Necessary argument

Features

selector-test-generator recursively walk though all directories starting from the execution folder or directory that is set as selector-path-arg. Then search for files with exported selectors. For exported selectors it creates __test__ folder with tests in current file directory. B

For example, we have a folder with selectors in the root project directory

<project>/
├── dir
│   └── withSelectorNested.js
├── state.js
├── withoutSelector.js
├── withSelector.js
└── withSelectorSecond.js

and after running the script

npx selector-test-generator <project>/ -s <project>/state.js

we get the following result

<project>/
├── dir
│   ├── __test__
│   │   └── withSelectorNested.js
│   └── withSelectorNested.js
├── state.js
├── __test__
│   ├── withSelector.js
│   └── withSelectorSecond.js
├── withoutSelector.js
├── withSelector.js
└── withSelectorSecond.js

of course, your test framework should be configured to search for tests in __test__ folder.

Tests are generated for explicitly and implicitly exported selectors.

For file withSelectors.js

import { createSelector } from 'reselect';

const unusedSelector = createSelector(
  ({ sub }) => sub,
  ({ loading }) => loading,
);

const implicityUsedSelector = createSelector(
  ({ sub }) => sub,
  ({ loading }) => loading,
);

const explicitlyUsedSelector = createSelector(
  ({ sub }) => sub,
  ({ property }) => property,
);

export const explicitlyUsedSelector2 = createSelector(
  ({ sub }) => sub,
  ({ undefinedProperty }) => undefinedProperty,
);

export const implicityUsedSelectorProxy = implicityUsedSelector;

export { explicitlyUsedSelector };

export default createSelector(
  ({ sub }) => sub,
  ({ loading }) => loading,
);

Selectors for which tests will be generated are createSelector, explicitlyUsedSelector, implicityUsedSelector, explicitlyUsedSelector2

Generated test selectors/__test__/withSelectors.js

import {
  explicitlyUsedSelector2,
  implicityUsedSelectorProxy,
  explicitlyUsedSelector,
} from '../withSelector.js';
import createSelector from '../withSelector.js';
import state from '../state.js';

describe('Application/Selectors/withSelector.js', () => {
  it('explicitlyUsedSelector2', () => {
    const received = explicitlyUsedSelector2(state);
    const expected = undefined;

    expect(received).toEqual(expected);
  });

  it('implicityUsedSelectorProxy', () => {
    const received = implicityUsedSelectorProxy(state);
    const expected = true;

    expect(received).toEqual(expected);
  });

  it('explicitlyUsedSelector', () => {
    const received = explicitlyUsedSelector(state);
    const expected = 'property';

    expect(received).toEqual(expected);
  });

  it('createSelector', () => {
    const received = createSelector(state);
    const expected = true;

    expect(received).toEqual(expected);
  });
});

License

MIT