This project is read-only.


Code coverage timeout issue


Hi there,

I just tried the new code coverage feature in 2.4.0 and got the same timeout error I was seeing previously with just running the tests. This was when running the tests both from the VS context menu and the console. The tests run fine when not doing coverage.

Any ideas?

Cheers, Andrew
Closed Dec 3, 2013 at 5:39 AM by mmanela


mmanela wrote May 1, 2013 at 4:07 AM

Is this using the same sample you posted here?
At least using that sample I was unable to repro.

LinusDillon wrote Jun 14, 2013 at 2:43 AM

We also seem to be having this issue. Tests run fine with via Visual Studio and TFS build server when code coverage is disabled, but fail with a timeout when I ask either to perform code coverage.

Have tried with a timeout of 60000 with no success.

mmanela wrote Jun 19, 2013 at 9:00 PM

Could you attach a zip that repros the timeout so I can validate my fix for your scenario?

AbraaoAlves wrote Jun 24, 2013 at 8:05 PM

You are probably using requeirejs or knockout. See this link

AbraaoAlves wrote Jun 25, 2013 at 1:55 PM

This problem occurs in the current version (2.4.1), just call the code coverage rjs-jasmine-solo.js

mmanela wrote Jun 28, 2013 at 5:54 AM

I will investigate this further, I think maybe upgrading to the new version of blanket.js may fix this.

mmanela wrote Jul 11, 2013 at 5:08 AM

Fixed in d30137163052

jeffmagic wrote May 15, 2014 at 8:57 PM

I am seeing this timeout issue with BlanketJS code coverage in Chutzpah

Any idea why this happens?

mmanela wrote May 15, 2014 at 9:33 PM

Can you file a new issue and attach a repro. There are many different causes to issues and often they can be solved by using the right config.

jeffmagic wrote May 15, 2014 at 10:09 PM

I played around with the configuration and excluded all but the tests and files under test and the issue is resolved. I think it was related to angular (when isn't it?).

Love Chutzpah!

So, my fix was to add CodeCoverageExclude in a Chutzpah.json and exclude angular stuff ( "/angular/js" or similar).


jeffmagic wrote May 15, 2014 at 10:10 PM

That should've read "*/angular*.js"

mmanela wrote May 15, 2014 at 10:47 PM

Ah yes. You should always exclude framework file from code coverage.