This is the command kcov 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
kcov - Code coverage analysis for compiled programs and Python scripts
kcov [options] outdir executable [ args for executable ]
This manual page documents briefly the kcov command. kcov is a code coverage tester for
ELF binaries, Python scripts and shell scripts. It allows collecting code coverage
information from executables without special compiler directives, and continuously
produces output from long-running applications.
Trace PID instead of executing executable, executable is optional in this case.
Setup limits for low/high coverage (default: 16,50).
Comma-separated list of paths to include in the report.
Comma-separated list of paths to exclude from the report.
Comma-separated list of path patterns to include in the report.
Comma-separated list of path patterns to exclude from the report.
Only collect coverage data, don't produce HTML/Cobertura output
Only report HTML/Cobertura output, don't collect data
Upload data to coveralls.io using secret repo_token or Travis CI service job ID id.
The ID is taken as a repo_token if it's longer or equal to 32 characters.
Number of path levels to show for common paths (default: 2).
Skip coverage collection for shared libraries (improves performance)
exit when the first process exits, i.e., honor the behavior of daemons. The default
behavior is to return to the console when the last process exits.
Set the python parser to use for Python programs (the default is python). Can be
used to run with Python 3 on systems where Python 2 is the default.
Set the bash parser to use for shell scripts (the default is /bin/bash).
Replace source file path P1 with P2, if found.
Check coverage for ./frodo and generate HTML output in /tmp/kcov and cobertura output in
kcov /tmp/kcov ./frodo
Check coverage for ./frodo but only include source files names with the string src/frodo
kcov --include-pattern=src/frodo /tmp/kcov ./frodo
Same as above but split collecting and reporting (perhaps on two different computers)
kcov --collect-only /tmp/kcov ./frodo
kcov --report-only --include-pattern=src/frodo /tmp/kcov ./frodo
The HTML output shows executed and non-executed lines of the source code. Some lines can
map to multiple instrumentation points, for example for inlined functions (where every
inlining of them will generate a separate instrumentation point). This is shown in the
left column as 1/3 for example, which means that one of the three instrumentation points
has been executed.
A special output link is [merged], which shows the union of all covered programs. This
can be useful for example when you have unit tests in multiple binaries which share a
subset of source files.
Kcov also outputs data in the Cobertura XML format, which allows integrating kcov output
in Jenkins (see http://cobertura.sf.net and http://jenkins-ci.org).
The Cobertura output is placed in a file named out-path/exec-filename/cobertura.xml.
Use kcov online using onworks.net services