Test: Add webpack unit tests.

Open
#61 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
build-system, testing

Research direction

Review the existing E2E tests that invoke webpack live or against previous builds, then identify how webpack() can run in memory. Define unit coverage for the webpack --watch regression using sinon.spy() on webpack 4 and webpack 5 hooks, and clarify additional cases before implementation. Done means the agreed in-memory unit tests cover the regression and pass for both webpack versions.

Written by the indexing model from the issue text.

Description

enhancement

Currently our tests just do E2E testing invoking webpack live or for previous builds. We should consider adding unit tests with running webpack() in memory for things like:

Dominant language
JavaScript
Stars
357
Forks
26
No merged PRs in 30d

Contributor guide

Open the contributing guide

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.

More from FormidableLabs/webpack-stats-plugin

All issues in FormidableLabs/webpack-stats-plugin

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.