Define where to put the instrumented file about blanket HOT 3 CLOSED

The problem with this, as I see it, is that if it's browser based the user needs to change the references.

so if they have "src/test.js" then in their test runner they need to reference "src-cov/test.js" in order to have the coverage run properly. If we hide the files from them it will make that change a lot more complicated. The question then becomes, do we generate a test runner for them, do we update their test runner, do we just provide instructions on how to modify it? Either way they'll need those files to be accessible to run their tests and get the coverage results.

When you min files it creates and puts them in a dist directory. I feel like this is similar.

The referencing of the new files is the bigger problem, imho. That's where things get messy. Either you automatically change references for people, or you need them to do it. Not ideal, either way.

from blanket.

Now one idea would be to use a requirejs type config model for loading the scripts.

So in the browser there would be a config file with a list of all the scripts, and this library would load, and instrument them all, and then load the instrumented scripts into the DOM so they have be tested.

In Node we would do like require("blanket")([array of scripts to use]) and the blanket require would load the original scripts in, instrument them, and then insert them into the require cache so the tests can be run.

This would require the user to change their test runners quite a bit, but it might be a way of eliminating the step of instrumenting files.

That might work?

from blanket.

okay, I changed it so that they configure the src and dest folders in the grunt config file. That seems the most logical to me to give them the option to put it wherever they want.

from blanket.