This is the command git-history-coverage that can be run in the OnWorks free hosting provider using one of our multiple free online workstations such as Ubuntu Online, Fedora Online, Windows online emulator or MAC OS online emulator
git-history-coverage - summarise test coverage for recent git commits
git-history-coverage [options] rev-list
Git-history-coverage extracts test coverage data produced by C and C++ programs compiled
with gcc --coverage, and correlates it to git commits, printing a coverage summary which
shows how well tested recent code changes have been. This is useful for nightly builds
and Continuous Integration systems such as Jenkins.
For the output of git-history-coverage to make any sense, the coverage data must be
generated by running code which corresponds to the last commit in the range specified by
When used without any options, git-history-coverage prints three summaries.
A summary of all the commits specified by rev-list.
A summary split up by each author represented in the set of commits specified by
A summary for each individual commit in the set of commits specified by rev-list.
For each of these summaries, git-history-coverage prints statistics showing how many lines
of code were in the commits, how many lines represent executable code (as opposed to
comments, test code, or infrastructure like Makefiles), and how many lines were actually
executed in tests.
Print the overall summary (with no options, all three summaries are printed).
Print the by author summary (with no options, all three summaries are printed).
Print the by commit summary (with no options, all three summaries are printed).
Look for .gcda files underneath the directory dir. This option is used to read
runtime coverage information written when a test program is run using the same
--gcda-prefix option to ggcov-run.
Use git-history-coverage online using onworks.net services