garris/BackstopJS

Puppeteer dev branch!

Open

#704 aberto em 16 de mar. de 2018

Ver no 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.

Guia do colaborador

Pilha de tecnologia
javascriptnodejs
Domain
testing
Tipo Issue
feature
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
4
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
over 1 week
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
stale
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
mostly clear
Prerequisites
Familiarity with BackstopJSUnderstanding of Puppeteer
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
25
Direção de pesquisa
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.