Wrong coverage with function named error

[yanickrochon]

I have to investigate more on what exactly can cause this, but here is the coverage of one of my files :

I had to add the console.log to see if these lines were actually being executed or not...

Especially when the function is actually being called and properly covered.

[yanickrochon]

Renaming the function error to throwErr (for example) seems to work. I don't know why error is not being covered and is an invalid function name, here.

[1602]

I guess that's because of regular expression that treat 'error' as special
case. good catch!

On 23 June 2014 16:53, Yanick Rochon [email protected] wrote:

Renaming the function error to throwErr (for example) seems to work. I
don't know why error is not being covered and is an invalid function
name, here.

—

Reply to this email directly or view it on GitHub
#6 (comment).