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

@chrisb-dev/auto-gen-store-component-unit-tests

v1.0.1

Published

We generate a lot of basic jest unit tests for components that connect to the store.

Downloads

1

Readme

Auto gen angular store component unit tests

We generate a lot of basic jest unit tests for components that connect to the store.

This app saves time by allowing us to auto generate a lot of these based on the setup of the component.

It assumed a component is an angular typescript component set up in the following way:

export class ExampleComponent implements OnInit {
    public exampleStoreItems$: Observable<ExampleStoreItemInterface[]>;

    constructor(
        private _store: Store<StateInterface>,
    ) {}

    public ngOnInit() {
        this.exampleStoreItems$ = this._store.select(selectExampleStoreItems);
    }

    public applyDiscount() {
        this._store.dispatch(applyDiscount());
    }
}

And from this it will generate the following tests:

describe('ngOnInit', () => {
    const initNgOnInitData = () => {
        const mockExampleStoreItems = Observable.of({});
        const store = initMockStore();
        store.select = jest.fn()
            .mockReturnValueOnce(mockExampleStoreItems);
        const exampleComponent = initExampleComponent(
            store,
        );

        return {
            exampleComponent,
            mockExampleStoreItems,
            store,
        };
    };

    test('Calls store.select with selectExampleStoreItems', () => {
        const {
            exampleComponent,
            store,
        } = initNgOnInitData();

        exampleComponent.ngOnInit();

        expect(store.select)
            .toHaveBeenCalledWith(selectExampleStoreItems);
    });

    test('Sets exampleStoreItems$ to the value from the store', () => {
        const {
            exampleComponent,
            mockExampleStoreItems,
        } = initNgOnInitData();

        exampleComponent.ngOnInit();

        expect(exampleComponent.exampleStoreItems$)
            .toBe(mockExampleStoreItems);
    });
    
});

describe('applyDiscount', () => {
    test('Dispatches a applyDiscount action to the store', () => {
        const store = initMockStore();
        const exampleComponent = initExampleComponent(
            store,
        );

        exampleComponent.applyDiscount();

        expect(store.dispatch)
            .toHaveBeenCalledWith(applyDiscount());
    });
});

This has to be done with ts-node as we're reading typescript to generate these tests.

Requirements

  • Node v8+
  • Npm v5+

Usage

  • npm i --save-dev @chrisb-dev/auto-gen-store-component-unit-tests

  • Add a script to package.json to run script: "auto-gen-organism-unit-tests": "ts-node node_modules/@chrisb-dev/auto-gen-store-component-unit-tests/index.ts"

  • Run the script with a component connected to the store: npm run auto-gen-organism-unit-tests ./src/organisms/basket/basket.component.ts

  • Alternatively, after installing, the script can just be run from the npm packages: ts-node node_modules/@chrisb-dev/auto-gen-store-component-unit-tests/index.ts ./src/organisms/basket/basket.component.ts

  • In either case replace ./src/organisms/basket/basket.component.ts with the path to the component you want to generate the data for.

Development

You can use the example file to try this out in development. To do this run: ts-node index.ts ./example/example.ts