QA:CodeCoverage: Difference between revisions

QA:CodeCoverage (view source)

553 bytes removed , 26 March 2009

→‎other changes: updating the doc after the .mozconfig change

canmove, Confirmed users

1,343

edits

@@ Line 207: / Line 207: @@
-=== other changes ===
+=== Jscoverage ===
-A bunch of javascript files gets ‘jar’ed’ into the
-Once the build is ready , all you have to do is to go into ~/mozcentral-dbg/dist/bin/chrome directory.
-You have to unjar all the java script files and modify the jar manifest files to point to appropriate un-jarred directories instead of   jar  files.
-Sounds confusing !! Don’t worry, please execute the following perl script expandJar.pl to do all that job for you.
-    Syntax : perl expandJar.pl ~/mozcentral-dbg/dist/bin/chrome
-Now, we have to instrument the javascript files.
 Code coverage for the Javascript part of the Firefox can be done in multiple ways. But using JSCoverage as the tool seemed to be the best way as JSCoverage is an open source tool.