Right know if you try to instrument the same js twice jscoverage produces this error:
[INFO] jscoverage: jscoverage.js: script contains line with more than 65,535 characters
May be jscoverage could detect the file is already instrumented and skip.
BTW, any hope of in place instrumenting, so no source/dest-dirs.... just providing source-dirs will instrument.
Any idea when next release comes out?
VELO
Suggestion for next release...
-
- Posts: 120
- Joined: 2008-10-11 6:52 pm
Re: Suggestion for next release...
I'm curious about the situation where that would be useful: You are instrumenting a directory that already contains (some) instrumented JavaScript files? Can you describe this in more detail?velo wrote:Right know if you try to instrument the same js twice jscoverage produces this error:
[INFO] jscoverage: jscoverage.js: script contains line with more than 65,535 characters
May be jscoverage could detect the file is already instrumented and skip.
I hesitate to add such a feature, for fear that I will receive irate complaints from users saying that jscoverage irrevocably mangled their JavaScript :/ Generally I would think you could just do this:velo wrote:BTW, any hope of in place instrumenting, so no source/dest-dirs.... just providing source-dirs will instrument.
Code: Select all
mv DIR DIR-original
jscoverage DIR-original DIR
Probably a few months. There are some features I want to add.velo wrote: Any idea when next release comes out?
VELO[/quote]
-
- Posts: 16
- Joined: 2009-06-08 7:04 pm
Re: Suggestion for next release...
That isn't useful =DEd wrote:I'm curious about the situation where that would be useful: You are instrumenting a directory that already contains (some) instrumented JavaScript files? Can you describe this in more detail?velo wrote:Right know if you try to instrument the same js twice jscoverage produces this error:
[INFO] jscoverage: jscoverage.js: script contains line with more than 65,535 characters
May be jscoverage could detect the file is already instrumented and skip.
In fact I got that by accident.
My builds are automated using maven, and maven automatically compile, package, test my application...
And I set maven to instrument my JS files using jscoverage before tests. But, sometimes I don't clean the last build, so I got this error.
-
- Posts: 120
- Joined: 2008-10-11 6:52 pm
Re: Suggestion for next release...
I think I understand now.velo wrote:That isn't useful =D
In fact I got that by accident.
So, if the jscoverage program detects that the source directory contains instrumented code, it should just print out a more comprehensible error message and then exit.
-
- Posts: 120
- Joined: 2008-10-11 6:52 pm
Re: Suggestion for next release...
The code in the Subversion repository now checks for instrumented files in the source directory.