Redis client mock object for unit testing
The goal of the
redis-mock project is to create a feature-complete mock of https://github.com/mranney/node_redis, so that it may be used interchangeably when writing unit tests for code that depends on
All operations are performed in-memory, why no Redis installation is required. 100% redis compatible (see cross verification)
$ npm install redis-mock --save-dev
The below code demonstrates a example of using the redis-mock client in node.js/io.js
var redis = require"redis-mock"client = rediscreateClient;
Currently implemented are the following redis commands:
If you want to add new tests to the test base it is important that they work too on node_redis (we are creating a mock...).
You can therefore run the tests using
redis instead of
redis-mock. To do so:
$ make check-tests
You will need to have a running instance of
redis on you machine and our tests use flushdb a lot so make sure you don't have anything important on it.
redis-mock is work in progress, feel free to report an issue
0.4.7 update devDependencies (should, mocha)
Copyright (c) 2012 Kristian Faeldt email@example.com
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.