--cover

[yields]

using duo api.

1. .use(cover)
2. if it's an entry instrument it
3. if it's a local dep of an entry like ./local.js instrument it.
4. profit

[stephenmathieson]

yes please

On Jul 7, 2014, at 2:53 PM, amir abu shareb [email protected] wrote:

using duo api.

.use(cover)
if it's an entry instrument it
if it's a local deep of an entry like ./local.js instrument it.
profit
—
Reply to this email directly or view it on GitHub.

[yields]

i don't think we should instrument in duo-test, it defeats the purpose of it being simple to configure.

instead i propose we add --cover <entry.js> to duo itself, duo will then instrument using a utility and expose a global like __cover__ or something that duo test can utilize to show stats / render.

any thoughts / feedback are welcome!

@matthewmueller

[matthewmueller]

any chance it could be a separate script and run under duo cover <entry>?

[yields]

don't think so :( there's the case were we do stuff like duo test.js > build.js and run the tests,
so instead we would do duo test.js --cover index.js > build.js.

[stephenmathieson]

any updates here? this would be super useful right now