Redis client mock object for unit testing
npm install redis-filebased-mockredis-filebased-mock
============
The goal of the redis-filebased-mock project is to create a feature-complete mock of node_redis, which may be used interchangeably when writing unit tests for code that depends on redis. redis-filebased-mock is a fork from redis-mock.
All operations are performed in-memory and filebased, so no Redis installation is required.
100% Redis-compatible (see Cross Verification)
```bash``
$ npm install redis-filebased-mock --save-dev
The below code demonstrates a example of using the redis-filebased-mock client in node.js/io.js
`js`
var redis = require("redis-filebased-mock"),
client = redis.createClient();
Currently implemented for redis-mock are the following redis commands, however for redis-filebased-mock is still working in progress:
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-filebased-mock. To do so:
``bash``
$ 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.
Copyright (c) 2012 Kristian Faeldt
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.