1. Docs
  2. Testing
  3. Functional

30 checks · visible behavior

Run the workflow. Observe the contract.

Functional checks exercise the queue as a consumer does, then verify the Playground presents those same transitions, flags, traces, validation rules, and related code.

10 queue + 20 Playground

All 30 Functional checks.

The two groups share the FIFO model but own different outcomes, so no case is counted twice.

Queue workflows · 10

  1. autoRun starts newly added work synchronously
  2. cooperative tasks execute in first-in-first-out order
  3. disabling autoRun leaves a new batch pending
  4. manual next selects the oldest pending task
  5. cooperative hand-offs drain a manually started batch
  6. stop prevents automatic execution after add
  7. next while stopped preserves the oldest task
  8. opening the stop gate does not execute work by itself
  9. explicit next after stop release resumes FIFO execution
  10. each task receives its queue as this

Playground behavior · 20

  1. playground cooperative preset exposes FIFO pending order
  2. playground cooperative next drains the complete trace
  3. playground manual next advances exactly one task
  4. playground manual hand-offs preserve FIFO order
  5. playground empty hand-off marks a manual queue idle
  6. playground stopped preset blocks next without consuming work
  7. playground stop release does not execute work by itself
  8. playground next after stop release drains FIFO work
  9. playground clear preserves flags and active trace
  10. playground reset restores constructor defaults
  11. playground custom tasks display oldest first
  12. playground rejects an empty custom label
  13. playground rejects a custom label over sixty characters
  14. playground rejects an unknown preset
  15. playground autoRun changes do not start existing work
  16. playground autoRun drains a new cooperative task
  17. playground autoRun leaves a new manual task active
  18. playground preset code describes the loaded queue
  19. playground added-task code matches its hand-off behavior
  20. playground queue controls expose their exact related code

Run this layer

Functional only, or inspect it live.

npm run test:functional
npm run test:playground