Re: JavaScript code coverage

2015-01-28 Thread Sylvestre Ledru
tions Strategic Plan is to provide > better data and metrics (including code coverage). Speaking as a member of > that organization, I'd love to deliver JavaScript code coverage. I'm pretty > sure we need the SpiderMonkey Team to step up and implement something. > Is it too har

Re: JavaScript code coverage

2015-01-27 Thread Gregory Szorc
code coverage). Speaking as a member of that organization, I'd love to deliver JavaScript code coverage. I'm pretty sure we need the SpiderMonkey Team to step up and implement something. On Tue, Jan 20, 2015 at 1:30 PM, Nick Fitzgerald wrote: > I recommend reading > https://devel

Re: JavaScript code coverage

2015-01-20 Thread Nick Fitzgerald
I recommend reading https://developer.mozilla.org/en-US/docs/Tools/Debugger-API or js/src/doc/Debugger/ for more information. On Tue, Jan 20, 2015 at 1:29 PM, Nick Fitzgerald wrote: > ​On Mon, Jan 19, 2015 at 12:36 PM, Joshua Cranmer [image: 🐧] < > pidgeo...@gmail.com> wrote: > >> Getting good c

Re: JavaScript code coverage

2015-01-20 Thread Nick Fitzgerald
​On Mon, Jan 19, 2015 at 12:36 PM, Joshua Cranmer 🐧 wrote: > Getting good code coverage (line and branch coverage) ultimately requires > fine-grained instrumentation (ideally bytecode-level) not presented by the > current Debugger. > ​I think you can get fine-grained enough data with the existi

Re: JavaScript code coverage

2015-01-20 Thread Philipp Kewisch
On 1/20/15 5:34 PM, Joshua Cranmer 🐧 wrote: > On 1/20/2015 4:37 AM, Nicolas B. Pierron wrote: >> Maybe some potential users will show up and mention that they are >> willing to get their hand dirty if we were to implement an Analysis >> API as discussed back in June. In which case we might be able

Re: JavaScript code coverage

2015-01-20 Thread Joshua Cranmer 🐧
On 1/20/2015 4:37 AM, Nicolas B. Pierron wrote: This "general design" is a pragmatic approach to help people implement different variant of taint-analysis without having to implement taint analysis in SpiderMonkey. Identically for code-coverage, how much time do you want to spend at doing code

Re: JavaScript code coverage

2015-01-20 Thread Nicolas B. Pierron
On 01/19/2015 09:36 PM, Joshua Cranmer 🐧 wrote: I've seen people bring up supporting this sort of stuff in the past, which usually tends to generate a flurry of "+1 this would be wonderful!" but ultimately everything peters out before anything gets done. The problem was not the solution, but th

JavaScript code coverage

2015-01-19 Thread Joshua Cranmer 🐧
Hi, you may know me as the guy who produces the code coverage results occasionally: . One persistent failure of producing code coverage is the inability to record code coverage in half of our codebase, the half that is written in JavaScript. There are s

Re: Code coverage [was: Re: Javascript code coverage ?]

2014-06-20 Thread Gregory Szorc
On 6/20/14, 5:00 AM, Joshua Cranmer 🐧 wrote: On 6/20/2014 4:25 AM, Sylvestre Ledru wrote: It takes around 26 hours on my workstation to run all the tests and about 4 days on (old?) Macbook pro. I haven't work on improving this yet. I am mildly distrustful of results that aren't running on as c

Re: Code coverage [was: Re: Javascript code coverage ?]

2014-06-20 Thread Boris Zbarsky
On 6/20/14, 8:00 AM, Joshua Cranmer 🐧 wrote: (there is 0% coverage of angle). That's not surprising given that the code coverage test is being done on Linux, is it? -Boris ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.

Re: Code coverage [was: Re: Javascript code coverage ?]

2014-06-20 Thread Sylvestre Ledru
On 20/06/2014 14:00, Joshua Cranmer 🐧 wrote: > On 6/20/2014 4:25 AM, Sylvestre Ledru wrote: >> It takes around 26 hours on my workstation to run all the tests >> and about 4 days on (old?) Macbook pro. >> I haven't work on improving this yet. > > I am mildly distrustful of results that aren't runn

Re: Code coverage [was: Re: Javascript code coverage ?]

2014-06-20 Thread Joshua Cranmer 🐧
On 6/20/2014 4:25 AM, Sylvestre Ledru wrote: It takes around 26 hours on my workstation to run all the tests and about 4 days on (old?) Macbook pro. I haven't work on improving this yet. I am mildly distrustful of results that aren't running on as close to the same configuration as our builder

Code coverage [was: Re: Javascript code coverage ?]

2014-06-20 Thread Sylvestre Ledru
Hello, Thanks for the various answers. On 17/06/2014 00:53, Clint Talbert wrote: > Inline > On 6/16/2014 10:23, Sylvestre Ledru wrote: >> Hello, >> >> I am working on providing weekly code coverage of Firefox code. >> For now, I am able to do that for C/C++ code. > Awesome. Where are you putt

Re: Javascript code coverage ?

2014-06-17 Thread Philipp Kewisch
On 6/17/14 4:28 AM, Joshua Cranmer 🐧 wrote: > I tried once again when the debugger API was added, but that again > didn't work for some reason (I've forgotten why long ago... probably > something to do with insufficiently exposing interesting globals?). Oh, one more thing, there are a few bugs rel

Re: Javascript code coverage ?

2014-06-16 Thread Joshua Cranmer 🐧
On 6/16/2014 12:23 PM, Sylvestre Ledru wrote: Hello, I am working on providing weekly code coverage of Firefox code. For now, I am able to do that for C/C++ code. I would like to know if anyone tried to generate code coverage recently on the Javascript code of Firefox (or Firefox OS)? Define

Re: Javascript code coverage ?

2014-06-16 Thread Clint Talbert
Inline On 6/16/2014 10:23, Sylvestre Ledru wrote: Hello, I am working on providing weekly code coverage of Firefox code. For now, I am able to do that for C/C++ code. Awesome. Where are you putting these reports? What is the workload used to generate those reports? I would like to know if

Re: Javascript code coverage ?

2014-06-16 Thread Ehsan Akhgari
On 2014-06-16, 1:23 PM, Sylvestre Ledru wrote: Hello, I am working on providing weekly code coverage of Firefox code. For now, I am able to do that for C/C++ code. Awesome, where can we find those reports? Thanks! Ehsan ___ dev-platform mailing lis

Re: Javascript code coverage ?

2014-06-16 Thread Philipp Kewisch
On 6/16/14 7:23 PM, Sylvestre Ledru wrote: > Hello, > > I am working on providing weekly code coverage of Firefox code. > For now, I am able to do that for C/C++ code. > > I would like to know if anyone tried to generate code coverage recently > on the Javascript code of Firefox (or Firefox OS)?

Javascript code coverage ?

2014-06-16 Thread Sylvestre Ledru
Hello, I am working on providing weekly code coverage of Firefox code. For now, I am able to do that for C/C++ code. I would like to know if anyone tried to generate code coverage recently on the Javascript code of Firefox (or Firefox OS)? I saw some b2g reports [1] talking about Coverage but I a