Using the NODE_ENV is nice simple solution but when you need more there is a great dependency injection module called rewire that adds a special setter and getter to modules so you can modify their behavior such as: inject mocks for other modules or globals like process, leak private variables
override variables within the module.<p>This is especially nice because you don't need to add any special if statements to the module code you just load your module under test using rewire instead of require.<p>// file: test-stats-rewire.js<p>var rewire = require('rewire');<p>var assert = require('assert');<p>var stats = rewire('./stats');<p>// leak private method sum for testing<p>var sum = stats.__get__('sum');<p>assert.equal(sum([1]), 1);<p>assert.equal(sum([1, 2, 3]), 6);
If you really want to buy into the module pattern, it seems like anything that's enough of a unit that you'd want to test could be in its own module.<p>In the example given, the sum function could be its own module that you require into the stats module. That way you could test them independently, and the stats module could simply expose its own appropriate methods.<p>This has the added benefit of making the sum function reusable.<p>Personally I prefer this approach to introducing environmental concerns into your code.
Very cool solution! I've also seen claims that the private methods of modules should not be tested, since they don't represent the public interface of the module and refactorings are likely to change the private methods. If the private methods are complicated enough to warrant testing on their own, ideally they should be extracted into their own module. Not sure if I agree but it's something to think about!
Don't test methods. Test behaviour that stands behind them. Unit in "unit testing" stands for behaviour not method/function. Private methods are private because they should not be exposed outside, never. Changing internal implementation of module should not crash test suite.
Why aren't you discussing the es6 loader which is available now?<p><a href="https://github.com/ModuleLoader/es6-module-loader" rel="nofollow">https://github.com/ModuleLoader/es6-module-loader</a><p>It can deal with both AMD and CommonJS modules, as well as es6 import/export. It does not need traceur and will work with today's JS. And is built upon the standards based System.js which basically provide loader hooks for node, JS, and even Web Components if they so desire.<p>It is sure nice to get rid of the forrest of <script> tags and not be concerned about order of dependencies.
I gave a lightning presentation on this subject last month. A better solution is to put the private methods into (sub)modules. This makes them public to the file system and gives you the ability to tune what you make public via your module API. Ideal for testing purposes and good for module structure in my opinion. The slides can be found here: <a href="https://speakerdeck.com/qubyte/writing-testable-private-methods-with-node-dot-js-modules" rel="nofollow">https://speakerdeck.com/qubyte/writing-testable-private-meth...</a>
exposing methods for the purpose of testing is bad design, whether or not you are only doing it in a test environment. if you have a method that is sufficiently complex and warrants its own testing, put it in it's own module file and test that module file on it's own - no need to break your design and modify your runtime module exports based on runtime environment checks<p><a href="http://lostechies.com/derickbailey/2014/01/03/semantics-modules-and-testing-why-and-how-i-test-internal-components-not-private-methods/" rel="nofollow">http://lostechies.com/derickbailey/2014/01/03/semantics-modu...</a>