linkedin / linkedin/spaniel

Use headless chrome instead of nightmare

Open
#83 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
92
Forks
34
PR merge metrics
No merged PRs in 30d

Description

Use something like puppeteer or chrome-debugging-client to get a "closer to reality" setup for testing

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the current Nightmare-based testing setup and its test entry points. Compare a headless Chrome approach such as Puppeteer or chrome-debugging-client, then confirm that the existing tests run in a setup closer to reality without losing their current coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
testing-qa
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.