JSCoverage is not 100%

[XavierAntoviaque]

Cf http://hackit.cx/jscoverage/jscoverage.html?test/jstest.html

Currently at 95% for hackit.js

[XavierAntoviaque (xavier-antoviaque)]

Added Proppy to the thread - he may have some good comments

[Johan Euphrosine (proppy)]

You could turn hackit_reload and hackit_alert function definition into:

var hackit = {
      document: document,
      alert: alert
};

This way it will generate coverage data for the declaration, and you will still be able to mockup implementation in tests.

[Vlad Dragu (vlad-dragu)]

Thanks Proppy, it worked

[Vlad Dragu (vlad-dragu)]

The coverage is at 99%. There is a single line of code not covered, a function that submits a form. I had to use a mock of that function in the js test because I couldn’t have the form submitted in the actual test.

[XavierAntoviaque (xavier-antoviaque)]

ok - I'll put it for a later version; next time proppy does a review, we'll see how to fix this.

[Vlad Dragu (vlad-dragu)]

The js coverage is 98% for alpha1.2 (hackit.js)

[Vlad Dragu (vlad-dragu)]

I added missing test and brought back the js coverage to 98% after the 2.2 version (missions and chat blocks).
The uncovered code is mocked functions

[XavierAntoviaque (xavier-antoviaque)]

jscoverage acts all weird on hackit.cx and shows low coverage % - cf http://hackit.cx/jscoverage/jscoverage.html?test/jstest.html