27 checks · connected boundaries
Join the surfaces. Verify the seams.
Integration checks cover APIs working together, asynchronous release, every supported package format, the easy-stack entry, classic-browser use, metadata, and the local documentation server.
5 interactions + 13 package + 9 server
All 27 Integration checks.
Each group owns a different seam: internal API composition, published consumption, or HTTP delivery.
Queue interactions · 5
- work added by an active task joins the FIFO tail
- an active task can stop the next hand-off
- replacement contents execute through the normal hand-off
- clear inside an active task removes only pending work
- an asynchronous callback releases the next FIFO task
Package and evidence boundaries · 13
- package primary ESM entry exports and executes Queue
- package primary CommonJS entry exports and executes Queue
- package ESM queue deep path remains executable
- package CommonJS queue deep path remains executable
- package ESM stack entry preserves LIFO order
- package CommonJS stack entry preserves LIFO order
- package ESM stack exposes the easy-stack 2.1 state contract
- package CommonJS stack exposes the easy-stack 2.1 state contract
- package classic script publishes a global Queue constructor
- package classic global executes the FIFO contract
- package metadata pins supported runtimes and dependencies
- package metadata exposes the supported public surface
- benchmark evidence matches the tagged baseline and chart claims
Local HTTP boundary · 9
- server resolves the site root inside the canonical directory
- server resolves documentation route directories
- server refuses encoded traversal outside the site root
- server returns HTML for overview and guide pages
- server returns the playground page and code surface
- server returns queue modules with JavaScript content types
- server returns repository artwork with image content types
- server distinguishes traversal and malformed URL failures
- server returns 404 for a missing local target
Run this layer
All seams, or one boundary.
npm run test:integration
npm run test:package
npm run test:server