Naively Programmable Module

    DefinitelyTyped icon, indicating that this package has TypeScript declarations provided by the separate @types/ioredis-mock package

    6.0.0 • Public • Published

    ioredis-mock · npm npm version Redis Compatibility: 29% semantic-release

    This library emulates ioredis by performing all operations in-memory. The best way to do integration testing against redis and ioredis is on a real redis-server instance. However, there are cases where mocking the redis-server is a better option.

    Cases like:

    • Your workflow already use a local redis-server instance for the dev server.
    • You're on a platform without an official redis release, that's even worse than using an emulator.
    • You're running tests on a CI, setting it up is complicated. If you combine it with CI that also run selenium acceptance testing it's even more complicated, as two redis-server instances on the same CI build is hard.
    • The GitHub repo have bots that run the testing suite and is limited through npm package.json install scripts and can't fire up servers. (Having Greenkeeper notifying you when a new release of ioredis is out and wether your code breaks or not is awesome).

    Check the compatibility table for supported redis commands.

    Usage (try it in your browser)

    const Redis = require('ioredis-mock');
    const redis = new Redis({
      // `` does not exist in `ioredis`, only `ioredis-mock`
      data: {
        user_next: '3',
        emails: {
          'clark@daily.planet': '1',
          '': '2',
        'user:1': { id: '1', username: 'superman', email: 'clark@daily.planet' },
        'user:2': { id: '2', username: 'batman', email: '' },
    // Basically use it just like ioredis

    Breaking API changes from v5

    Before v6, each instance of ioredis-mock lived in isolation:

    const Redis = require('ioredis-mock');
    const redis1 = new Redis();
    const redis2 = new Redis();
    await redis1.set('foo', 'bar');
    console.log(await redis1.get('foo'), await redis2.get('foo')); // 'bar', null

    In v6 the internals were rewritten to behave more like real life redis, if the host and port is the same, the context is now shared:

    const Redis = require('ioredis-mock');
    const redis1 = new Redis();
    const redis2 = new Redis();
    const redis3 = new Redis({ port: 6380 }); // 6379 is the default port
    await redis1.set('foo', 'bar');
      await redis1.get('foo'), // 'bar'
      await redis2.get('foo'), // 'bar'
      await redis3.get('foo') // null

    And since ioredis-mock now persist data between instances, you'll likely need to run flushall between testing suites:

    const Redis = require('ioredis-mock');
    afterEach((done) => {
      new Redis().flushall().then(() => done());

    createConnectedClient is deprecated

    Replace it with .duplicate() or use another new Redis instance.

    Configuring Jest

    Use the jest specific bundle when setting up mocks:

    jest.mock('ioredis', () => require('ioredis-mock/jest'));

    The ioredis-mock/jest bundle inlines imports from ioredis that ioredis-mock rely on. Thus you can map ioredis import identifiers to ioredis-mock/jest without dealing with circular issues.

    Pub/Sub channels

    We also support redis publish/subscribe channels. Like ioredis, you need two clients:

    const Redis = require('ioredis-mock');
    const redisPub = new Redis();
    const redisSub = new Redis();
    redisSub.on('message', (channel, message) => {
      console.log(`Received ${message} from ${channel}`);
    redisPub.publish('emails', 'clark@daily.planet');


    By default, ioredis-mock uses the native Promise library. If you need (or prefer) bluebird promises, set Redis.Promise:

    var Promise = require('bluebird');
    var Redis = require('ioredis-mock');
    Redis.Promise = Promise;

    Lua scripting

    You can use the defineCommand to define custom commands using lua or eval to directly execute lua code.

    In order to create custom commands, using lua scripting, ioredis exposes the defineCommand method.

    You could define a custom command MULTIPLY which accepts one key and one argument. A redis key, where you can get the multiplicand, and an argument which will be the multiplicator:

    const Redis = require('ioredis-mock');
    const redis = new Redis({ data: { 'k1': 5 } });
    const commandDefinition: { numberOfKeys: 1, lua: 'return KEYS[1] * ARGV[1]' };
    redis.defineCommand('MULTIPLY', commandDefinition) // defineCommand(name, definition)
      // now we can call our brand new multiply command as an ordinary command
      .then(() => redis.multiply('k1', 10));
      .then(result => {
        expect(result).toBe(5 * 10);

    You can also achieve the same effect by using the eval command:

    const Redis = require('ioredis-mock');
    const redis = new Redis({ data: { k1: 5 } });
    const result = redis.eval(`return"GET", "k1") * 10`);
    expect(result).toBe(5 * 10);

    note we are calling the ordinary redis GET command by using the global redis object's call method.

    As a difference from ioredis we currently don't support:

    • dynamic key number by passing the number of keys as the first argument of the command.
    • automatic definition of the custom command buffer companion (i.e. for the custom command multiply the multiplyBuffer which returns values using Buffer.from(...))
    • the evalsha command
    • the script command


    Work on Cluster support has started, the current implementation is minimal and PRs welcome #359

    const Redis = require('ioredis-mock');
    const cluster = new Redis.Cluster(['redis://localhost:7001']);
    const nodes = cluster.nodes;


    You can check the roadmap project page, and the compat table, to see how close we are to feature parity with ioredis.

    I need a feature not listed here

    Just create an issue and tell us all about it or submit a PR with it! 😄


    npm i ioredis-mock

    DownloadsWeekly Downloads






    Unpacked Size

    529 kB

    Total Files


    Last publish


    • stipsan