Daphne Maddox

This issue is biting me. What I tried to do is: 1) use Closure Builder to write a list of the files that I need to run in order --...

``` blanket: { options: {}, build: { files: { 'src-cov/': ['src/'] } } }, ``` Run command: ``` $ grunt blanket ```

I see the instrumented file in my file system, of course. I also see this same source code in the HTML report in the test runner after running the tests....

Ok, I figured out how to run the normal mocha reporter (I think): ``` ``` Same result. This is with blanket 1.1.5 or the development snapshot (which I just tried...

Does it matter that in the instrumentation it's referring to the "src" directory even though all of the action is actually taking place in the "src-cov" directory? I wouldn't think...

I thought about that (and tried it). When I remove the data-cover-only attribute, no blanket report appears at all. Before posting my question I even added a new attribute to...

I'm manually instrumenting because without doing so blanket coverage **doesn't** see the actual tests being run -- it sees the goog.require stuff happening but not the tests themselves. When it...

(left out the word doesn't -- without manually instrumenting, it **doesn't** see the tests being run)

Something tells me we're getting somewhere... but we're not there yet :) So for whatever reason (I don't know too much about data- variables, I'm getting a lower-cased value when...

found it. line 4497: ``` // coverage_data.files = window._$blanket; SCS coverage_data.files = window._$jscoverage; ``` Whoo hoo! Sir, you rock.