waterline-fakes
Utilities to make it easier to fake out waterline models and collections for unit testing.
description
When unit testing controllers or services in Sails.js, it can be helpful to replace model and collection interaction
results with fake results, so that you're only testing the one layer of your code that you are focusing on. This package
exposes some factories to generate objects and methods that would take the place of normal Sails model or collection
methods.
install
npm i --save-dev waterline-fakes
api
var waterlineFakes = require('waterline-fakes');
using fakeWaterlineChainMethod(options)
Used to replace a method on a Collection, that would normally be followed by a call to
.exec(function (err, results)) {}
. A normal block of code that you would want to test may look something like this:
list: function (req, res) {
Pets.find(req.query).exec(function (err, pets) {
if (err) {
res.send(500, { error: 'internal server error' });
return;
}
res.send(200, pets);
});
}
To test the error condition of this controller action using mocha
, you could do something like this:
var req = require('supertest');
var sinon = require('sinon');
var expect = require('chai').expect;
var fakeWaterlineChainMethod = require('waterline-fakes').fakeWaterlineChainMethod;
describe('the list method', function () {
describe('when an error occurs looking up the pets', function () {
beforeEach(function () {
sinon.stub(Pets, 'find', fakeWaterlineChainMethod({
err: new Error('boom');
}));
});
it('returns 500 status code and error json', function (done) {
req(sails.hooks.http.server)
.get('/pets')
.expect(500)
.expect('Content-Type', /json/)
.end(function (err, res) {
expect(err).to.not.exist();
expect(res.body).to.deep.equal({
error: 'internal server error'
});
done();
});
});
});
});
fakeWaterlineChainMethod api
var fakeWaterlineChainMethod = require('waterline-fakes').fakeWaterlineChainMethod;
var fakeMethod = fakeWaterlineChainMethod({
err: {},
result: {}
});
using fakeWaterlineModel(options)
Used to simulate an actual Waterline model, if your controller or service code interacts with the model directly. This
is usually passed as the result
option to fakeWaterlineChainMethod when needed.
Take this other example controller action:
update: function (req, res) {
Pets.findOneById(req.params.id).exec(function (err, pet) {
if (err) {
res.send(500, { error: 'internal server error' });
return;
}
if (!pet) {
res.send(404, { error: 'not found' });
return;
}
pet.name = req.body.name;
pet.color = req.body.color;
pet.type = req.body.type;
pet.save(function (err, updatedPet) {
if (err) {
res.send(500, { error: 'internal server error' });
return;
}
res.send(200, updatedPet);
};
});
}
You could test the error condition of the pet.save()
using the following mocha
test:
var req = require('supertest');
var sinon = require('sinon');
var expect = require('chai').expect;
var waterlineFakes = require('waterline-fakes');
var fakeWaterlineChainMethod = waterlineFakes.fakeWaterlineChainMethod;
var fakeWaterlineModel = waterlineFakes.fakeWaterlineModel;
describe('the update method', function () {
describe('when an error occurs while saving the updated pet', function () {
beforeEach(function () {
var fakePet = fakeWaterlineModel({
save: { err: new Error('boom') }
});
sinon.stub(Pets, 'findOneById', fakeWaterlineChainMethod({ result: fakePet }));
});
it('returns 500 status code and error json', function (done) {
req(sails.hooks.http.server)
.put('/pets/foo')
.send({
name: 'Lenny',
type: 'golden retriever',
color: 'champagne'
}).expect(500)
.expect('Content-Type', /json/)
.end(function (err, res) {
expect(err).to.not.exist();
expect(res.body).to.deep.equal({
error: 'internal server error'
});
done();
});
});
});
});
fakeWaterlineModel api
var fakeWaterlineModel = require('waterline-fakes').fakeWaterlineModel;
var fakeModel = fakeWaterlineModel({
props: {},
destroy: {
err: {}
},
save: {
err: {},
result: {}
}
});
contributing
To contribute, see CONTRIBUTING.md
license
MIT