What is Code Coverage?¶
Code coverage essentially measures how often certain lines are hit, branches taken or conditions met in a program, given some test that you run on it.
There are two very important things to keep in mind when talking about code coverage:
If a certain branch of code is not hit at all while running tests, then those tests will never be able to find a bug in this particular piece of the code.
If a certain branch of code is executed (even very often), this still is not a clear indication of the quality of a test. It could be that a test exercises the code but does not actually check that the code performs correctly.
As a conclusion, we can use code coverage to find areas that need (more) tests, but we cannot use it to confirm that certain areas are well tested.
Firefox Code Coverage reports¶
The generated reports can be found at https://coverage.moz.tools/. The reports can be filtered by platform and/or test suite.
We also generate a report of all totally uncovered files, which can be found at https://coverage.moz.tools/#view=zero. You can use this to find areas of code that should be tested, or code that is no longer used (dead code, which could be removed).
C/C++ Code Coverage on Firefox¶
There are several ways to get C/C++ coverage information for mozilla-central, including creating your own coverage builds. The next sections describe the available options.
Generate Code Coverage report from a try build (or any other CI build)¶
To spin a code coverage build, you need to select the linux64-ccov platform (use –full when using the fuzzy selector to get the ccov builds to show up).
E.g. for a try build:
./mach try fuzzy -q 'linux64-ccov'
There are two options now, you can either generate the report locally or use a one-click loaner.
Generate report using a one-click loaner¶
Select the B job on Treeherder and get a one-click loaner.
In the loaner, download and execute the script https://github.com/mozilla/code-coverage/blob/master/report/firefox_code_coverage/codecoverage.py:
wget https://raw.githubusercontent.com/mozilla/code-coverage/master/report/firefox_code_coverage/codecoverage.py python codecoverage.py
This command will automatically generate a HTML report of the code coverage information in the report subdirectory in your current working directory.
Generate report locally¶
Create and activate a new virtualenv, then run:
pip install firefox-code-coverage
Given a treeherder linux64-ccov build (with its branch, e.g. `mozilla-central` or `try`, and revision, the tip commit hash of your push), run the following command:
firefox-code-coverage PATH/TO/MOZILLA/SRC/DIR/ BRANCH REVISION
This command will automatically download code coverage artifacts from the treeherder build and generate an HTML report of the code coverage information. The report will be stored in the report subdirectory in your current working directory.
Creating your own Coverage Build¶
On Linux, Windows and Mac OS X it is straightforward to generate an
instrumented build using GCC or Clang. Adding the following lines to
.mozconfig file should be sufficient:
# Enable code coverage ac_add_options --enable-coverage # Needed for e10s: # With the sandbox, content processes can't write updated coverage counters in the gcda files. ac_add_options --disable-sandbox
Some additional options might be needed, check the code-coverage mozconfigs used on CI to be sure: browser/config/mozconfigs/linux64/code-coverage, browser/config/mozconfigs/win64/code-coverage, browser/config/mozconfigs/macosx64/code-coverage.
Make sure you are not running with artifact build enabled, as it can prevent coverage artifacts from being created.
You can then create your build as usual. Once the build is complete, you can run any tests/tools you would like to run and the coverage data gets automatically written to special files. In order to view/process this data, we recommend using the grcov tool, a tool to manage and visualize gcov results. You can also use the same process explained earlier for CI builds.
Debugging Failing Tests on the Try Server¶
When code coverage is run through a push to try, all the data that is created is ingested by ActiveData and processed into a different data format for analysis. Anytime a code coverage run generates *.gcda and *.gcno files, ActiveData starts working. Now, sometimes, a test will permanently fail when it is running on a build that is instrumented with GCOV. To debug these issues without overloading ActiveData with garbage coverage data, open the file taskcluster/gecko_taskgraph/transforms/test/__init__.py and add the following line,
right after this line of code:
Now when you push to try to debug some failing tests, or anything else, there will not be any code coverage artifacts uploaded from the build machines or from the test machines.
JS Debugger Per Test Code Coverage on Firefox¶
Generate Per Test Code Coverage from a try build (or any other treeherder build)¶
To spin a code coverage build, you need to select the linux64-jsdcov platform. E.g. for a try build:
./mach try fuzzy -q 'linux64-jsdcov'
Generate Per Test Code Coverage Locally¶
To generate the JSON files containing coverage information locally, simply
add an extra argument called
--jscov-dir-prefix which accepts a
directory as it’s input and stores the resulting data in that directory.
For example, to collect code coverage for the entire Mochitest suite:
./mach mochitest --jscov-dir-prefix /PATH/TO/COVERAGE/DIR/
Currently, only the Mochitest and Xpcshell test suites have this capability.