Last modified: 2014-11-18 18:07:30 UTC
Any plans of having JSCover (JavaScript code coverage analysis) being integrated and run by Jenkins (in away that is usable for core and extensions as well)? [1] http://tntim96.github.io/JSCover/ [2] http://tntim96.github.io/JSCover/example-qunit/out/jscoverage.html?test/index.html [3] http://tntim96.github.io/JSCover/manual/manual.xml#automatingPhantomJS [4] http://tntim96.github.io/JSCover/manual/manual.xml#automatingAnt
I think we want QUnit tests on a few more extensions before adding code coverage. Thus lowering priority.
Both jscoverage and the new fork JSCover seem to have quite a nasty (though from a quick look, hard to avoid) implementation that involves instrumenting files. Though that in and of itself isn't a problem, it does this by running a static file server and proxying javascript files through its instrumentor and using some kind of HTML parser (another Java class dependency) to catch inline scripts even (not sure). This isn't going to work straight up with MediaWiki since we generate HTML dynamically (e.g mediawiki-core/index.php) and load things through ResourceLoader.
The JSCover JAR (JSCover-all.jar) is all custom code and only includes the Rhino library (i.e. no Jetty, Log4J, Apache-commons or other library dependencies). Also, there is no HTML parser. When a JavaScript file is requested via JSCover's web or proxy server, JSCover instruments the specified JavaScript only. Whether the HTML is generated dynamically or not doesn't affect JSCover in proxy-mode. For proxy documentation, take a look at: http://tntim96.github.io/JSCover/manual/manual.xml#gettingStartedProxy ...and a working proxy example at: https://github.com/tntim96/JSCover-samples/blob/master/src/test/java/jscover/webdriver/jasmine/WebDriverUnderscoreProxyTest.java Let me know if there are any changes required to JSCover that would assist you.
I'm not sure this will get any attention in a foreseeable future therefore closing this one.
Javascript coverage is still something we need. Nobody looked at integrating it in Jenkins yet though.
JSCover didn't work out very well. I've standardised on istanbul[1] for the moment. There are qunit[2] and karma[3] integrations. Both of which we've been using for OOjs and VisualEditor these past few months. They have command-line and HTML reporters. [1] http://gotwarlost.github.io/istanbul/ https://github.com/gotwarlost/istanbul [2] https://github.com/asciidisco/grunt-qunit-istanbul [3] https://github.com/karma-runner/karma-qunit https://github.com/karma-runner/karma-coverage
