raphamorim/origami.js

Migrate tests structure based on phanthomjs to other runner option

Open

#73 opened on Mar 13, 2018

View on GitHub
 (5 comments) (0 reactions) (0 assignees)JavaScript (757 stars) (61 forks)batch import
help wanted

Description

Currently Phantomjs is no longer maintained. I was wondering if make sense to move to Puppeteer or other option to run origamijs tests.

Contributor guide

Tech stack
javascript
Domain
testing
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
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
JavaScript fundamentalsExperience with test runnersFamiliarity with PhantomJS/Puppeteer
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate the current test setup in the repository, likely using PhantomJS. Review the 5 comments in issue #73 for any proposed solutions or blockers. Examine package.json and test configuration files to understand how tests are run. Consider migrating to Puppeteer or headless Chrome, and ensure the new setup integrates with the existing CI (e.g., Travis). Test that all existing tests pass after migration.
Migrate tests structure based on phanthomjs to other runner option · raphamorim/origami.js#73 | Good First Issue