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

@firstlutfi/cypress-fixture-faker

v1.1.0

Published

A package to generate fixture data using Faker.js for Cypress tests

Downloads

4

Readme

Cypress Fixture Faker

Use a faker.js method right from your Cypress fixture file.

Background Context

When writing Cypress tests, the framework provide you with a fixture folder where you can store your data in a JSON format. However, since it is a JSON file, you can't put a JS function directly. The common way is to create a helper function that receives a JSON object and then transform any attributes that you want using a faker.js method.

This package aims to remove the hassle by enabling you to write a faker.js method as the value of your fixture file.

Installation

Install with npm

  npm install @firstlutfi/cypress-fixture-faker

Or if you use Yarn

  yarn add @firstlutfi/cypress-fixture-faker

Usage/Examples

See the following JSON example:

{
    "normal_text": "This will be a normal text",
    "email": "{{ internet.email }}",
    "full_name": "Mr. {{ person.firstName }} {{ person.lastName }}",
    "with_depth": {
        "age": "{{ number.int({ \"min\": 10, \"max\": 100 }) }}"
    },
    "with_array": [
        "{{ color.human }}",
        "{{ color.human }}",
        "{{ color.human }}"
    ]
}

Use it in your Cypress spec file

import example from '../fixtures/example.json';
import { cff } from '@firstlutfi/cypress-fixture-faker'

describe('Cypress Fixture Faker Test Suite', () => {
    it('Should be able to parse data from fixture', () => {
        const generatedData = cff.transform(example);
    });
});

If you try to log the output, the data would become:

{
    "normal_text": "This will be a normal text",
    "email": "[email protected]",
    "full_name": "Mr. Jaylon Kuhn",
    "with_depth": {
        "age": "90"
    },
    "with_array": [
        "olive",
        "pink",
        "gold"
    ]
}

Notes

  • In order to read the faker.js method, the value of the attributes needs to be a string. Therefore, currently, all returned values will also be a string.
  • All values inside the double curly braces {{ }} have to be a valid faker.js method. You need to ensure that your test data do not require any literal double curly braces.
  • If you need named parameters for the faker.js method, you need to escape the doublequotes using backslash (see the example above for the "age" attribute).