FAQ

1. What problem does this solve?
2. When I use Blanket.js with QUnit locally it fails, why?

## What problem does this solve?

Existing code coverage tools for JavaScript typically don't meet the following requirements:

• Written only in JavaScript
• Don't need to modify source files
• Don't need to create physical instrumented copies of files
• Long time to setup and configure
• Not friendly to novice developers; those who need the most encouragement to write tests!

Blanket.js aims to meet all these requirements by:

• Being 100% JavaScript
• No changes needed to source files, and only minor changes needed to test runners
• All source files are instrumented "live" and no copies of files are created
• Easy to install, configure, and use.
• As easy as installing and using QUnit itself.

## When I use Blanket.js with QUnit locally it fails, why?

Blanket.js uses a modified version of RequireJS, which loads source files using AJAX. Unfortunately, when running locally Chrome blocks these attempts to access files.
You can either run a web server locally, or start chrome using special flags.