Cypress Integration

Cypress is a JavaScript End to End Testing Framework. It is a great tool for testing your website and Pixeleye integrates seamlessly with it.

Quick start

Installation

We require the Pixeleye cli tool and Cypress tool

npm install pixeleye @pixeleye/cypress --save-dev

npm install pixeleye @pixeleye/cypress --save-dev

Get a project token

You can get a project token from the Pixeleye dashboard. You will need this to authenticate your project with Pixeleye.

See Getting Started for more information.

Create a pixeleye.config.{js,ts} file

/** @type {import('pixeleye').Config} */
const config = {
  token: "YOUR_PROJECT_TOKEN",
  // or
  // token: process.env.PIXELEYE_PROJECT_TOKEN,
  // ...
};

export default config;

/** @type {import('pixeleye').Config} */
const config = {
  token: "YOUR_PROJECT_TOKEN",
  // or
  // token: process.env.PIXELEYE_PROJECT_TOKEN,
  // ...
};

export default config;

Adding to your tests

import { pixeleyeSnapshot } from "@pixeleye/cypress";

// ...

  await pixeleyeSnapshot({
    name: "landing-header",
  });

// ...

import { pixeleyeSnapshot } from "@pixeleye/cypress";

// ...

  await pixeleyeSnapshot({
    name: "landing-header",
  });

// ...

Running the Pixeleye CLI

We can pass our cypress run command to the Pixeleye CLI.

npm run pixeleye exec -- cypress run

npm run pixeleye exec -- cypress run

API Reference

fn pixeleyeSnapshot(options)

Captures a snapshot of the current page.

Options - name (required)

• Type: string

The name of the snapshot. This helps us identity which snapshots to compare with as well as giving a nice name in our dashboard.

Options - variant

• Type: string
• Default: undefined

The variant of the snapshot. It's up to you how you use this, but it's useful for capturing different states of the same component. E.g., a collection of snapshots with the name button could have variants of primary, secondary, etc.

Options - fullPage

• Type: boolean
• Default: false

Whether to capture the full page. If set to true, the entire page will be captured. If set to false, only the current viewport will be captured.

Options - selector

• Type: string
• Default: undefined

The selector of the element to capture. If set, only the element matching the selector will be captured. If not set, the entire page will be captured.

Options - waitForSelectors

• Type: string[]
• Default: []

The selectors to wait for before capturing the snapshot. If set, we will wait for all the selectors to appear before capturing the snapshot. If not set, we will not wait for any selectors. This doesn't effect the selector option.

Options - devices

• Type: DeviceDescriptor[]
• Default: Defined in pixeleye.config.ts

The devices to capture the snapshot on. If set, the snapshot will be captured on each device. If not set, the snapshot will be captured on the current viewport.

This will override the devices option set in pixeleye.config.ts.

Options - waitForStatus

• Type: boolean
• Default: false

If set to true, we will wait for the build to finish processing and return the status of the build to stdout. This is useful for CI/CD environments where you want to capture the status of the build.

Options - maskSelectors

• Type: string[]
• Default: []

The selectors to mask. If set, the selectors will be masked with the color defined in maskColor. If not set, no selectors will be masked.

Options - maskColor

• Type: string
• Default: #FF00FF (pink)

The color to mask the selectors with. This can be any valid CSS color. We recommend using a color that is not used anywhere else on the page.

Options - css

• Type: string
• Default: undefined

The CSS to inject into the page. This can be used to hide elements that you don't want to capture. For example, you may want to hide a cookie banner that appears on the page.

This css is append to the css defined in pixeleye.config.ts. Anything which needs overriding there should be overridden via css here.