--cover #12

Activity

1. stephenmathieson commented on Jul 7, 2014

   

   stephenmathieson

   on Jul 7, 2014

   Contributor

   More actions

   yes please

   On Jul 7, 2014, at 2:53 PM, amir abu shareb notifications@github.com 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.
2. yields commented on Jul 9, 2014

   

   yields

   on Jul 9, 2014

   ContributorAuthor

   More actions

   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
3. matthewmueller commented on Jul 9, 2014

   

   matthewmueller

   on Jul 9, 2014

   Contributor

   More actions

   any chance it could be a separate script and run under duo cover <entry>?
4. yields commented on Jul 9, 2014

   

   yields

   on Jul 9, 2014

   ContributorAuthor

   More actions

   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.
5. stephenmathieson commented on Oct 30, 2014

   

   stephenmathieson

   on Oct 30, 2014

   Contributor

   More actions

   any updates here? this would be super useful right now