Behavioral suite · B001–B008

Eight outcomes seen through a consumer's eyes.

Behavioral cases combine public operations into acceptance scenarios, then cross the browser boundary to verify actual clicks, visible state, editor synchronization, errors, and recovery.

Unique case catalog

  1. B001 resource cleanup runs newest acquisition first
  2. B002 urgent work added during a pause runs before the older backlog
  3. B003 maintenance mode keeps late urgent work gated and releases it first
  4. B004 a user steps through the manual preset and sees each visible transition
  5. B005 custom editor changes survive activity until the user synchronizes
  6. B006 a user sees source preparation fail and can recover on the next run
  7. B007 a user can stop active code and prevent further output
  8. B008 Given a served import map, when the bare package runs, then visible LIFO state changes

Run this suite

npm run test:behavioral
npm run test:behavioral:chrome

easy-stack works with bundlers and without a bundler. Bundlers resolve the bare package import normally; native browser ESM uses an import map with no build or transpilation step. B001–B003 are host-neutral acceptance scenarios replayed by Node and native coverage. B004–B008 drive the locally served Playground DOM in installed Chrome; B008 proves that native path, while the editor scenarios also cross the opaque Worker boundary.

Next suiteIntegration