← ClaudeAtlas

bullmq-testslisted

Use whenever a Node.js or TypeScript service uses BullMQ and its queues or workers need tests: producers, worker processors, retries, backoff and repeat jobs, FlowProducer parent-child jobs and QueueEvents, against real Redis (Docker, Testcontainers) or ioredis-mock.
testland/qa · ★ 13 · Testing & QA · score 80
Install: claude install-skill testland/qa
# bullmq-tests ## Overview Per [github.com/taskforcesh/bullmq][bm-gh]: [bm-gh]: https://github.com/taskforcesh/bullmq > "The fastest, most reliable, Redis-based distributed queue for > Node. Carefully written for rock solid stability and atomicity." BullMQ's testing model differs from Sidekiq / Celery: there is no "fake mode" or in-memory queue substitute. Tests use real Redis (Docker / Testcontainers) or stub it via `ioredis-mock`. Tests typically validate: queue add → worker processor → completion event. ## When to use - The repo has BullMQ Queue + Worker definitions in Node.js / TS. - The user writes tests for queue producer logic (controllers, service layers). - The user writes tests for worker processor business logic. - A test verifies retry / backoff / FlowProducer parent-child semantics. ## How to use 1. Install `bullmq` (add `ioredis-mock` for stricter unit isolation) - see Install. 2. Point tests at a shared connection: a real Redis (Docker / Testcontainers) for integration, or `ioredis-mock` for pure unit tests of producer logic. 3. Test the producer - enqueue, then assert on `queue.getJobs(['waiting'])`; `drain()` between tests and `close()` in `afterAll` (see Worked example). 4. Test the worker - call the processor function directly for unit tests, or run a real `Worker` + `QueueEvents` for integration (see Worked example). 5. For retry / backoff, repeat-job, FlowProducer flows, and CI wiring, see [references/advanced-patterns-and-ci.md](references/a