garris/BackstopJS

Puppeteer dev branch!

Open

#704 ouverte le 16 mars 2018

Voir sur GitHub
 (45 commentaires) (15 réactions) (0 assignés)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.

Guide contributeur

Stack technique
javascriptnodejs
Domaine
testing
Type d'issue
feature
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
4
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
over 1 week
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
stale
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
mostly clear
Prérequis
Familiarity with BackstopJSUnderstanding of Puppeteer
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
25
Direction de recherche
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.