title: Ember CLI and code coverage
body: <p>Has anyone managed to get code coverage working with an Ember CLI project?</p>
  
  <p>I've tried using <a href="http://blanketjs.org/" rel="nofollow noreferrer">blanket.js</a> and <a href="https://github.com/gotwarlost/istanbul" rel="nofollow noreferrer">istanbul</a>, as have others <a href="https://stackoverflow.com/questions/24498486/blanket-js-not-working-with-qunit-in-ember-cli">here</a>, <a href="https://stackoverflow.com/questions/25907782/ember-cli-importing-blanket-js-causes-test-runners-to-hang">here</a> and <a href="https://stackoverflow.com/questions/24494839/ember-cli-code-coverage-reports">here</a>, neither with any success. I've managed to get each to actually produce a coverage report but the report either says 0% (istanbul) or 100% (blanket.js), and there's no way the current tests provide 100% coverage.</p>
  
  <p>The built project JavaScript file that Ember CLI produces contains all of the project's source files with each file's contents being output onto one, sometimes massive, line. So even if the coverage tool was able to produce the actual coverage metrics for the code in the built file there's then the issue of viewing the results. God only knows how you would link this back to the original source files?</p>
  
  <p>Ember CLI is great and seems popular so I'm surprised more people haven’t had this issue. Perhaps others aren't as bothered by code coverage or maybe most just get it working without issue and I'm missing something.</p>