- Browser testing
- Node
- RequireJS
- Mocha in the browser
- Jasmine
- Backbone
- CoffeeScript in the browser
- CoffeeScript in node
- Custom reporter
- Branch Tracking
- How much jQuery does Bootstrap use?
A classic example of browser testing with blanket coverage can be found in /test/lib-tests. This is blanket covering the blanket code (eating our own dog food).
Node testing can be seen in /test/test-node. These are blanket's own node based tests.
If you already use RequireJS in your test runner, it's no problem, blanket will work around it. See an example in /test/requirejs
Mocha can be run in the browser, and blanket seamlessly integrates with it. All you need to do is reference the mocha adapter when you reference the blanket script, and the rest is done for you.
Check out an example in /test/mocha-browser
Blanket comes with QUnit support by default, but Jasmine (or any other test runner) can be supported using an adapter (or a custom build!).
An example of Jasmine support can be seen in /test/jasmine
Backbone, or any external library, doesn't have any affect on blanket. The Backbone Koans test suite (by Addy Osmani) illustrates the compatibility.
If your test runner tests source files written in coffee script, blanket still has you covered. Using a custom loader, coffeescript files are compiled, instrumented, and tested.
See coffeescript support in /test/coffee_script
If your mocha tests use coffee script source files, blanket still has you covered.
See an example in /test/test-node/
You can easily create your own reporters for blanket. See a frivolously simple example in /test/custom-reporter
Blanket can track untouched branches. You can view a simple example in /test/branchTracking
You can cover dependencies of your source files to see what percentage of a certain library you use.
You can see this in action by viewing /test/bootstrap and seeing that Twitter Bootstrap uses almost 50% of jQuery code!