js-queue
  1. Docs
  2. Testing

Small checks · clear ownership

Four layers. Ninety checks.

vanilla-test 2.1.1 runs focused Unit, Functional, Integration, and Regression checks. No duplicated cases. The queue-facing layers run unchanged in Node and real Google Chrome.

92 focused checks

Four independent layers.

Each check owns one behavior or boundary. Open a layer to see every named case without turning this overview into a long test log.

10 Unit

One API fact at a time

Exports, defaults, isolated storage, return values, task references, size, and contents replacement.

See all 10 checks → 30 Functional

Observable queue workflows

FIFO flow, manual release, stop gates, task context, Playground controls, validation, state, trace, and related code.

See all 30 checks → 27 Integration

Boundaries working together

Active-task interactions, asynchronous release, ESM, CommonJS, stack, browser global, metadata, benchmark evidence, local HTTP, and media types.

See all 27 checks → 25 Regression

Failures that stay fixed

Atomic validation, thrown-task recovery, the no-WeakMap runtime contract, documentation links, local assets, testing attribution, and deployment gates.

See all 25 checks → 
npm test
npm run test:unit
npm run test:functional
npm run test:integration
npm run test:regression
npm run test:core
npm run test:playground
npm run test:package
npm run test:server
npm run test:docs

Native V8 evidence

Every core path is required.

The coverage configuration includes only the shipped ESM queue. Node and Chrome collect their own native V8 data and each enforce the same floor.

100%statements required
100%branches required
100%functions required
100%lines required
npm run coverage
# or independently
npm run coverage:node
npm run coverage:chrome
No source instrumentation or bundle enters the path.

The JavaScript measured by both collectors is the same queue.js consumers import.

Open Node reportOpen Chrome report

Delivery gates

Runtime and package shape are explicit.

CI runs vanilla-test across platforms and the exact Node floor, collects native Chrome coverage, reproduces the benchmark, and installs the packed artifact. Pages deploys only after that main run succeeds.

Continuous integration jobs
GateRuntimesProves
PlatformsNode 24 · Linux, macOS, WindowsThe full suite behaves consistently across operating systems.
Runtime floorNode 22.13ESM and synchronous CommonJS share one source without warnings.
CoverageNode 24 + Chrome StableBoth native V8 collectors satisfy every 100% gate.
BenchmarkNode 24The tagged 3.0.0 baseline and private-field runtime are measured again.
PackageNode 24The tarball installs and resolves ESM, CommonJS, browser, and stack files.
Open CI runsRead test source