browserify v2 version of proxyquire.
Proxies browserify's require in order to make overriding dependencies during testing easy while staying totally unobstrusive.
Table of Contents generated with DocToc
- Features
- Installation
- Example
- API
- proxyquire.browserify()
- proxyquire(request: String, stubs: Object)
- noCallThru
- More Examples
- no changes to your code are necessary
- non overriden methods of a module behave like the original
- mocking framework agnostic, if it can stub a function then it works with proxyquireify
- "use strict" compliant
- automatic injection of
require
calls to ensure the module you are testing gets bundled
npm install proxyquireify
foo.js:
var bar = require('./bar');
module.exports = function () {
return bar.kinder() + ' ist ' + bar.wunder();
};
foo.test.js:
var proxyquire = require('proxyquireify')(require);
var stubs = {
'./bar': {
wunder: function () { return 'wirklich wunderbar'; }
, kinder: function () { return 'schokolade'; }
}
};
var foo = proxyquire('./src/foo', stubs);
console.log(foo());
browserify.build.js:
var proxyquire = require('proxyquireify');
proxyquire.browserify()
.require(require.resolve('./foo.test'), { entry: true })
.bundle({ debug: true })
.pipe(fs.createWriteStream(__dirname + '/bundle.js'));
load it in the browser and see:
schokolade ist wirklich wunderbar
To be used in build script instead of browserify()
, autmatically adapts browserify to work for tests and injects
require overrides into all modules via a browserify transform.
proxyquire.browserify()
.require(require.resolve('./test'), { entry: true })
.bundle()
.pipe(fs.createWriteStream(__dirname + '/bundle.js'));
- request: path to the module to be tested e.g.,
../lib/foo
- stubs: key/value pairs of the form
{ modulePath: stub, ... }
- module paths are relative to the tested module not the test file
- therefore specify it exactly as in the require statement inside the tested file
- values themselves are key/value pairs of functions/properties and the appropriate override
var proxyquire = require('proxyquireify')(require);
var barStub = { wunder: function () { 'really wonderful'; } };
var foo = proxyquire('./foo', { './bar': barStub })
In order for browserify to include the module you are testing in the bundle, proxyquireify will inject a
require()
call for every module you are proxyquireing. So in the above example require('./foo')
will be injected at
the top of your test file.
By default proxyquireify calls the function defined on the original dependency whenever it is not found on the stub.
If you prefer a more strict behavior you can prevent callThru on a per module or per stub basis.
If callThru is disabled, you can stub out modules that weren't even included in the bundle. Note, that unlike in proxquire, there is no option to prevent call thru globally.
// Prevent callThru for path module only
var foo = proxyquire('./foo', {
path: {
extname: function (file) { ... }
, '@noCallThru': true
}
, fs: { readdir: function (..) { .. } }
});
// Prevent call thru for all contained stubs (path and fs)
var foo = proxyquire('./foo', {
path: {
extname: function (file) { ... }
}
, fs: { readdir: function (..) { .. } }
, '@noCallThru': true
});
// Prevent call thru for all stubs except path
var foo = proxyquire('./foo', {
path: {
extname: function (file) { ... }
, '@noCallThru': false
}
, fs: { readdir: function (..) { .. } }
, '@noCallThru': true
});