Hi, 1.)I have been using JSCover file system instrumentation mode. 2.) I have successfully instrumented my .js files . 3.)ALso the instrumented .js files has been attached to the site. 4.) Now I am manually doing some tests in the instrumented files. 5.)So my last aim is to collect the coverage data generated. 6.)So for testing i am calling on the .js files jscoverage_serializeCoverageToJSON() method from a javascript file. 7)I am not using PhantomJS,or webdriver or selenium 8.)I am storing the outcome like :: var str=jscoverage_serializeCoverageToJSON(); Then printing it like document.write(str); I am not getting the coverage report.........Like how much lines got executed.......

If i am wrong then how to write it a javascript file to store the data coming from jscoverage_serializeCoverageToJSON(); also if i am writing in javascript then u cannot save it locally in a file....(i may hv to use node.js)

I'm running some tests manually on a JS application using proxy mode. Would you provide me some instructions on how to gather JS Coverage when running manual tests please?

I instrumented the code,started running web server in proxy mode, started JSCOver as well and then started running few manual tests on the instrumented code. I see all the file structure getting created in the target folder. However, coverage is zero.

Could you let me know if I'm missing something here?

There are error messages as followings when I use jscover and adding the option "--include-unloaded-js" in proxy mode.

start proxy command - java -jar JSCover-all-2.0.3.jar -ws --proxy --port=3128 --report-dir=./jscover/output --document-root=/Users/weiding/Git/fmw-bi-qafmk/bitools-utils/podapiutil/coverage/carbs/js/plugins --local-storage --include-unloaded-js

I do not have any idea about this issue. Is it a bug when saving the coverage data?

Detailed error messages- 20180403 11:20:00.439,227,SEVERE,"Error saving coverage data",jscover.server.InstrumentingRequestHandler, com.google.gson.JsonSyntaxException: com.google.gson.stream.MalformedJsonException: Unterminated string at line 1 column 8370739 path $..branchData.5[1].evalFalse at com.google.gson.Gson.fromJson(Gson.java:902) at com.google.gson.Gson.fromJson(Gson.java:852) at com.google.gson.Gson.fromJson(Gson.java:801) at com.google.gson.Gson.fromJson(Gson.java:773) at jscover.report.JSONDataMerger.jsonToMap(JSONDataMerger.java:404) at jscover.report.JSONDataSaver.saveJSONData(JSONDataSaver.java:382) at jscover.server.InstrumentingRequestHandler.storeReport(InstrumentingRequestHandler.java:421) at jscover.server.InstrumentingRequestHandler.handlePostOrPut(InstrumentingRequestHandler.java:391) at jscover.server.HttpServer.run(HttpServer.java:418) Caused by: com.google.gson.stream.MalformedJsonException: Unterminated string at line 1 column 8370739 path $..branchData.5[1].evalFalse at com.google.gson.stream.JsonReader.syntaxError(JsonReader.java:1559) at com.google.gson.stream.JsonReader.nextQuotedValue(JsonReader.java:1017) at com.google.gson.stream.JsonReader.nextName(JsonReader.java:787) at com.google.gson.internal.bind.ObjectTypeAdapter.read(ObjectTypeAdapter.java:70) at com.google.gson.internal.bind.ObjectTypeAdapter.read(ObjectTypeAdapter.java:61) at com.google.gson.internal.bind.ObjectTypeAdapter.read(ObjectTypeAdapter.java:70) at com.google.gson.internal.bind.ObjectTypeAdapter.read(ObjectTypeAdapter.java:70) at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.read(TypeAdapterRuntimeTypeWrapper.java:41) at com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeAdapterFactory.java:187) at com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeAdapterFactory.java:145) at com.google.gson.Gson.fromJson(Gson.java:887) ... 8 more

20180403 11:25:32.769,441,SEVERE,"Error saving coverage data",jscover.server.InstrumentingRequestHandler, com.google.gson.JsonSyntaxException: java.io.EOFException: End of input at line 1 column 8376000 path $..functionData[35] at com.google.gson.Gson.fromJson(Gson.java:897) at com.google.gson.Gson.fromJson(Gson.java:852) at com.google.gson.Gson.fromJson(Gson.java:801) at com.google.gson.Gson.fromJson(Gson.java:773) at jscover.report.JSONDataMerger.jsonToMap(JSONDataMerger.java:404) at jscover.report.JSONDataSaver.saveJSONData(JSONDataSaver.java:382) at jscover.server.InstrumentingRequestHandler.storeReport(InstrumentingRequestHandler.java:421) at jscover.server.InstrumentingRequestHandler.handlePostOrPut(InstrumentingRequestHandler.java:391) at jscover.server.HttpServer.run(HttpServer.java:418) Caused by: java.io.EOFException: End of input at line 1 column 8376000 path $..functionData[35] at com.google.gson.stream.JsonReader.nextNonWhitespace(JsonReader.java:1393) at com.google.gson.stream.JsonReader.doPeek(JsonReader.java:467) at com.google.gson.stream.JsonReader.hasNext(JsonReader.java:414) at com.google.gson.internal.bind.ObjectTypeAdapter.read(ObjectTypeAdapter.java:60) at com.google.gson.internal.bind.ObjectTypeAdapter.read(ObjectTypeAdapter.java:70) at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.read(TypeAdapterRuntimeTypeWrapper.java:41) at com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeAdapterFactory.java:187) at com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeAdapterFactory.java:145) at com.google.gson.Gson.fromJson(Gson.java:887) ... 8 more

I created a small script that hacks localStorage support into the JSCover instrumentation. (I had difficulty getting my Rails Capybara tests to run with any of execution modes in the manual, it always seemed to click in the wrong frame or close the other tab before I could get the coverage data out reliably.)

All it does is add these two lines of code at the start:

if (typeof(_$jscoverage)=='undefined' && localStorage["jscov"]) _$jscoverage= JSON.parse(localStorage["jscov"])
window.onbeforeunload = function(){if (typeof(_$jscoverage) != 'undefined' ) localStorage["jscov"]=jscoverage_serializeCoverageToJSON()}

An then there is one line of code in my test setup that empties out the localStorage at the start and at the end a bit that captures the coverage data. And a little rake script to automate the whole process.

Question: This all works great as long as the branch detection is off, I couldn't figure out how the branch data can be reconstructed from JSON.

Feature request: It would be nice to have an option for JSCover to add the lines needed for localStorage automatically.

Reposting this question https://sourceforge.net/p/jscover/discussion/general/thread/102a5fba/

Sorry if the question is not right on target, but there is a use case we need to fulfill, will try to describe here.

Esp with impending ES6 and Babel adoption (where babel will transpile es6 to es5 code), we are being asked to look into what we can do to show original sources in coverage report, so is there a way to use source maps with jscover? Source maps could be either for babel transpilation or for minification. Either way, goal is to see coverage for original source somehow.

Also since jscover does store original-src in the report, if source map is also available on disk somewhere, can that somehow be leveraged in jscover?

Hello, and thanks in advance for this very helpful tool. We are currently working with JSCover on a large scale development project and we've successfully integrated the Cobertura results into our Jenkins build process. We are having some issues interpreting the results however, here is an example of how they can look for a test case:

The report indicates that 2 out 2 packages have been covered, and 4 out of 4 files have been covered. While it's true that 4 files have been covered, there are far more than 4 total files in the project (number of files are in the hundreds, and packages in the dozens), so it should be 4 out of XXX, right? Similary lines covered says 6 out of 945, but 945 is only the total for the covered files, not the entire project.

Is there something you can immedietly point to that we're doing wrong which causes this, or are we interpreting the results incorrectly? We seem to be referencing the source code correctly when creating the Cobertura XML, because if we go into the "breakdown by file" it correctly displays the source code of the covered files atleast. Thanks in advance

I've just updated from jscoverage to JSCover (using as proxy instrumentation server) and now have some troubles with POST-requests containing binary data ... the requests get stuck at the proxy and run into a socket timeout of 1 minute.

Here are some details:

• the POST-requests that cause the problem are multipart-posts containing binary data (but small ones handled as 1 request ... < 1KB)
• the binary data inside that POST-request is from an XML-file with UTF-8 encoding with byte-order-mark (BOM) / without the BOM the problem does not occur
• I'm using the java system config -Dfile.encoding=UTF-8
• these requests are not instrumented but handled by the proxy
• I think the problem is that the POST-data is handled as text (toStringNoClose) which leads into encoding problems that the binary data length is different from the encoded character-text length and therefor the stream read operation can't read any more data -> timeout

Here is a screenshot of some debug output logs for more details ...

It would be much better to forward (especially not instrumented requests) exactly with the same content as they are received (copy stream data as binary data - not as encoded characters). POST-data requests could also contain real binary data - maybe they should be by-passed even at a higher level.

Kind regards, Klaus.

Hi, Such as the title, my action as following:

run command java -Dfile.encoding=UTF-8 -jar /JSCover-all.jar -fs --local-storage ./js1 ./js2 in WebServer js folder.

In this time, use chrome open the web, is ok, look like no problem, I can run jscoverage_serializeCoverageToJSON(); in chrome console get jscoverage.json string when I run my test case.

but, if refresh the current page or use other browsers open it, such as chrome console throws an error, Refused to evaluate a string as JaveScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "default-src 'self'.

I don't understand, my usage is right?

If I hope to use File Mode compiled js file in webserver, what should I do?

thank you for your time.

Hello Everyone . I am a beginner in JSCover . I just want to know , how to begin with file system mode .

what i have done till now -

1. Downloaded JSCover and paste my all the files and test cases in the doc/example/ folder .
2. Create server by calling example/server/jscover-server.bat or by cmd
3. By Opening perticular link on browser (i.e. localhost:8080/ ) , it showed to me code coverage of my files and also generate the report in the target folder .

what i have to do -

1. I have integrate JSCover with my project , that will automatically test my js file by taking test cases without creating server , just show me the result or report.

what i want to know -

1. I think for achieving my goal , i have to begin on file system automation .
2. please help me from where i should start ?
3. do i need to use selenium , phantomJs , htmlunit etc ?
4. I want to modify JScover according to my own requirements , please guide me .
5. what is proxy mode , is it useful for me ? thanks in advance

Since switching from the JSCover-all.jar to the jcenter jscover Gradle "com.github.tntim96:JSCover:1.0.23" dependency JSCover no longer produces correct coverage data.

The jscoverage.json file has around 95k json and around 60k 0 bytes (Hex: 0x00).

I also tried version 1.0.24 and 1.0.25 with the same results.

I start JSCover using ant with:

  <property name="jscover.main.jar" location="com.github.tntim96-JSCover.jar"/>

  <path id="jscover.classpath">
    <pathelement location="org.mozilla-rhino.jar"/>
    <pathelement location="${jscover.main.jar}"/>
  </path>

  <target name="jscover-start">
    <java classname="jscover.Main" classpathref="jscover.classpath" fork="true" spawn="true">
    ...

The log file doesn't contain anything more useful than the message I get during shutdown:

[java] Exception in thread "main" java.lang.RuntimeException: org.mozilla.javascript.json.JsonParser$ParseException: Unexpected token: 
[java] 	at jscover.report.JSONDataMerger.jsonToMap(JSONDataMerger.java:436)
[java] 	at jscover.report.Main.saveCoberturaXml(Main.java:465)
[java] 	at jscover.report.Main.runReport(Main.java:409)
[java] 	at jscover.report.Main.runMain(Main.java:394)
[java] 	at jscover.report.Main.main(Main.java:366)
[java] Caused by: org.mozilla.javascript.json.JsonParser$ParseException: Unexpected token: 
[java] 	at org.mozilla.javascript.json.JsonParser.readValue(JsonParser.java:82)
[java] 	at org.mozilla.javascript.json.JsonParser.readArray(JsonParser.java:167)
[java] 	at org.mozilla.javascript.json.JsonParser.readValue(JsonParser.java:60)
[java] 	at org.mozilla.javascript.json.JsonParser.readObject(JsonParser.java:119)
[java] 	at org.mozilla.javascript.json.JsonParser.readValue(JsonParser.java:58)
[java] 	at org.mozilla.javascript.json.JsonParser.readObject(JsonParser.java:119)
[java] 	at org.mozilla.javascript.json.JsonParser.readValue(JsonParser.java:58)
[java] 	at org.mozilla.javascript.json.JsonParser.parseValue(JsonParser.java:44)
[java] 	at jscover.report.JSONDataMerger.jsonToMap(JSONDataMerger.java:412)
[java] 	... 4 more

From jscover.log

20161221 17:21:22.604,912,INFO,"Saving/merging JSON with existing JSON",jscover.report.JSONDataSaver,
20161221 17:21:22.604,912,INFO,"Saving/merging JSON with existing JSON",jscover.report.JSONDataSaver,
20161221 17:21:22.607,912,SEVERE,"Error saving coverage data",jscover.server.InstrumentingRequestHandler,
java.lang.RuntimeException: org.mozilla.javascript.json.JsonParser$ParseException: Unexpected token: n
        at jscover.report.JSONDataMerger.jsonToMap(JSONDataMerger.java:436)
        at jscover.report.JSONDataMerger.mergeJSONCoverageStrings(JSONDataMerger.java:368)
        at jscover.report.JSONDataSaver.saveJSONData(JSONDataSaver.java:373)
        at jscover.server.InstrumentingRequestHandler.storeReport(InstrumentingRequestHandler.java:421)
        at jscover.server.InstrumentingRequestHandler.handlePostOrPut(InstrumentingRequestHandler.java:391)
        at jscover.server.HttpServer.run(HttpServer.java:418)
Caused by: org.mozilla.javascript.json.JsonParser$ParseException: Unexpected token: n
        at org.mozilla.javascript.json.JsonParser.readNull(JsonParser.java:367)
        at org.mozilla.javascript.json.JsonParser.readValue(JsonParser.java:68)
        at org.mozilla.javascript.json.JsonParser.readArray(JsonParser.java:167)
        at org.mozilla.javascript.json.JsonParser.readValue(JsonParser.java:60)
        at org.mozilla.javascript.json.JsonParser.readObject(JsonParser.java:119)
        at org.mozilla.javascript.json.JsonParser.readValue(JsonParser.java:58)
        at org.mozilla.javascript.json.JsonParser.readObject(JsonParser.java:119)
        at org.mozilla.javascript.json.JsonParser.readValue(JsonParser.java:58)
        at org.mozilla.javascript.json.JsonParser.parseValue(JsonParser.java:44)
        at jscover.report.JSONDataMerger.jsonToMap(JSONDataMerger.java:412)
        ... 5 more

20161221 17:21:22.607,912,FINE,"Sending response status:200 OK mime:text/plain",jscover.server.HttpServer,

Any Ideas?

As for our project , we need more detail coverage data about every js file, so can you add the following info to classElement.

        classElement.setAttribute("lines-covered", "" + file.getCodeLinesCoveredCount());
        classElement.setAttribute("lines-valid", "" + file.getCodeLineCount());
        classElement.setAttribute("branchs-covered", "" + file.getBranchesCoveredCount());
        classElement.setAttribute("branchs-valid", "" + file.getBranchCount());

we will be very appreciate , if you add this. thank you very much !

After added , the following xml is what we want

This is a test refactoring.

Problem: The Exception Handling test smell occurs when a test method explicitly a passing or failing of a test method is dependent on the production method throwing an exception.

Solution: Use JUnit's exception handling to automatically pass/fail the test instead of writing custom exception handling code or throwing an exception. In this case, JUnit 4.13 assertThrows() was used to properly handle the expected exception.

Result: Before:

try {
    mainHelper.checkDependantClasses(dependantClasses, "MANIFEST-NO-CLASS-PATH.MF");
    fail("Should have thrown exception");
} catch(IllegalStateException e) {
    String message = e.getMessage();
    assertThat(message, equalTo("Could not find the 'Class-Path' attribute in the manifest 'MANIFEST-NO-CLASS-PATH.MF'"));
}

After:

IllegalStateException thrown = assertThrows(IllegalStateException.class, () ->
            mainHelper.checkDependantClasses(dependantClasses, "MANIFEST-NO-CLASS-PATH.MF"));
assertTrue(thrown.getMessage().contains("Could not find the 'Class-Path' attribute in the manifest " +
            "'MANIFEST-NO-CLASS-PATH.MF'"));

How (and if) this is implemented is currently wide open. The JSCoverage approach has been partially implemented, however this only works in the JSCoverage report, so am not keen to add something limited in this way except for those migrating from JSCoverage.

Things to consider:

• How should merging be handled
• Should statistics be affected (i.e. add a fake increment or teat ignored code as comments)
• How could this work in other reports (e.g. LCOV)

If branch coverage has been disabled (the coverage contains no branch coverage). The 3 columns concerning the branch coverage are not useful and should be hidden.