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

cypress-splitio

v2.0.1

Published

Execute your tests based on Split.io splits and treatments

Downloads

4

Readme

cypress-splitio

npm Gitlab pipeline status

This plugin stores your toggles with treatments from split.io as environment variables so you can access them via Cypress.env(). Also it allows you to store splits with treatments as fixtures

Installation

npm install --save-dev cypress-splitio

or

yarn add --dev cypress-splitio

Configure

Since this is a plugin, you will need to modify your file ./cypress/plugins/index.js to look something like this:

module.exports = (on, config) => {
  config = splitioPlugin(config)
  return config
}

Here is an example of splits.json structure

{
    'feature-one': 'on',
    'feature-two': 'off',
    'feature-three': 'custom'
}

If you want to turn off fixture creation set fixture = false.

module.exports = (on, config) => {
  config = splitioPlugin(config, fixture = false)
  return config
}

Getting splits and current treatments

Once you update your plugins config, you can now get all current splits via Cypress.env('split-name') or via splits.json fixture. Just specify a valid split environment SDK key like this:

npx cypress run --env SPLITIO_CONFIG=YOUR_SDK_KEY_HERE

Getting splits based on custom attributes

Use the following syntax if you need to get your split configuration based on custom attributes

npx cypress run --env SPLITIO_CONFIG='{"KEY":"YOUR_SDK_KEY_HERE","license":"beta"}'

Running tests based on splits

You can now have a different behavior in your test based on split environment variable:

describe( 'Dashboard page', () => {
    it( '...', () => {
        if(Cypress.env('split-one') === 'on') {
            ...
        } else {
            ...
        }
    } );
} );

Or you can do the same with a fixture

describe( 'Dashboard page', () => {
  it( '...', () => {
    cy.fixture( 'splits' ).then( ( json ) => {
      if(json['feature-one'] === 'on') {
        ...
      } else {
        ...
      }
    } );
  } );
} );

You can also use cypress-skip-test plugin to define when to execute or skip a test

describe( 'Dashboard page', () => {
    it( '...', () => {
        cy.skipOn(Cypress.env('split-two') === 'on');
    } );
} );

Or like this

onlyOn(Cypress.env('split-two') === 'on', () => {
  describe('foo', () => {
    it('works', () => {...})
  })
});

Contribute

Want to help or have a suggestion? Open a new ticket and we can discuss it or submit a pull request.

License

MIT