garris/BackstopJS

Puppeteer dev branch!

Open

#704 opened on Mar 16, 2018

View on GitHub
 (45 comments) (15 reactions) (0 assignees)JavaScript (6,510 stars) (601 forks)batch import
enhancementhelp wanted

Description

This is happening! image

This branch... https://github.com/garris/BackstopJS/tree/puppeteer

is tracking this branch... https://github.com/krisdigital/BackstopJS

Interested in contributing? ...please coordinate with @krisdigital.

What you need to know...

  • The Puppeteer engine option will be released as soon as we are at feature parity with Chromy and Phantom.
  • We will continue to support Phantom, Chromy and Puppeteer moving forward.
  • You are awesome.

Contributor guide

Tech stack
javascriptnodejs
Domain
testing
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Familiarity with BackstopJSUnderstanding of Puppeteer
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
This issue is a tracking issue for adding Puppeteer as a new engine to BackstopJS. The work is being done in a separate branch (puppeteer) and coordinated with @krisdigital. A contributor should review the branch to understand current progress and what remains to achieve feature parity with existing Chromy and Phantom engines. The issue has been open since 2018 with many comments, indicating previous discussion. No pull requests are linked, so the work is in progress but may be stalled.