Skip to content

An opinionated example config for backstopjs which supports testing multiple projects

Notifications You must be signed in to change notification settings

mmunz/backstopjs-config

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

backstop-config

This is an opinionated BackstopJS config which allows to test multiple projects while sharing basic setup. But everything can be overwritten from project configs.

Requirements

The backstop.js script uses the minimist package to parse commandline arguments. You may install that package globally or create a package.json in this directory.

Setup

Create a basic backstopjs config with

backstop init

Then copy the defaults and sites folder and the backstop.js and cookies.json files from this project into your backstop folder and edit them according to your needs.

Configuration

Defaults

Defaults shared between all projects are located in the defaults folder.

Sites (Projects)

Individual projects/sites are configured in the sites directory. For each project create a folder with the project id as name and a config.js file inside it.

The values defined in these project level config.js files are merged with the default configs.

See (sites/example/config.js) for more details.

Executing the backstopjs tests

The --config argument is required. You also need to provide the id of a project to test, e.g.

backstop reference --config=backstop.js --id=example
backstop test --config=backstop.js --id=example

About

An opinionated example config for backstopjs which supports testing multiple projects

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published