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

xstate-test-cypress

v1.5.0

Published

Utilities for adapting @xstate/test to work more easily with cypress 7+

Downloads

2

Readme

xstate-test-cypress

All Contributors

Utilities for adapting @xstate/test to work more easily with cypress 7+

Usage

Basic usage is as follows, for more complete usage with types refer to /cypress/integration/todo.spec.ts and /cypress/components/* folder for component testing example.

Note that testContext is the object that you pass in to plan.test(...), it has no relation to the context of the machine.

import {
  checkCoverage,
  createCypressMachine,
  createCypressModel,
  simpleExecutePlan
} from 'xstate-test-cypress';

const testMachine = createCypressMachine(
  {
    states: {
      parent: {
        on: {
          SIMPLE: 'other'
        },
        states: {
          child: {
            on: { CASES: 'other' }
          }
        }
      },
      other: {}
    }
  },
  {
    parent: (testContext) => cy.get('something').should('be.visible'),
    'parent.child': (testContext) => {
      cy.get('something').should('have.length', 2);
      // Note that all these functions must return a Chainable
      return cy.get('something-else').should('contain', 'some text');
    }
  }
);

const testModel = createCypressModel(testMachine, {
  SIMPLE: () => cy.get('button').eq(0).click(),
  CASES: {
    cases: [{ value: 'Value one' }, { value: 'Value 2' }],
    exec: (testContext, testCase) => {
      testContext.someCounter += 1;
      return cy.focused().clear().type(`${testCase.value}{enter}`);
    }
  }
});

context('example tests', () => {
  simpleExecutePlan(testModel.getSimplePathPlans(), () => {
    cy.visit('/');
    return { someCounter: 1 };
  });
  checkCoverage(testModel);
});

context('updated tests', () => {
  simpleExecutePlan(
    testModel
      .update(
        { other: () => cy.log('new state check') },
        { SIMPLE: () => cy.log('new event execution') }
      )
      .getSimplePathPlans(),
    () => {
      cy.visit('/');
      return { someCounter: 1 };
    }
  );
  checkCoverage(testModel);
});

Test application is forked from the TodoMVC site.

Contributors ✨

Thanks goes to these wonderful people (emoji key):

This project follows the all-contributors specification. Contributions of any kind welcome!