coverage Documentation

Official Emacs Lisp developer resources and documentation for google/coverage with 28 stars. Verified technical context for AI.

28 stars Emacs Lisp 1 file Β· ~575 tokens
RAW Doc

File: README.md

coverage.el generates code coverage profiles and overlays them in GNU
Emacs buffers.

Adding support for new languages and tools is easy. Currently
coverage.el supports Go coverage profiles, gcov profiles, and lcov
profiles.

Installation

Add to .emacs.el

text
(add-to-list 'load-path "/path/to/coverage/directory")
(require 'coverage)

The package requires GNU Emacs 24.3+.

To test the package after installation

  • open coverage-test.el
  • Run eval-buffer (M-x eval-buffer RET)
  • Run ert (M-x ert RET t RET)

Usage

Open and follow instructions in files

  • examples/go/example.go
  • examples/c/example.c

More information is in the Commentary section in the coverage.el file.

Contributing

See CONTRIBUTING.md.

Disclaimer

This is not an official Google product.


File: CONTRIBUTING.md

Want to contribute? Great! First, read this page (including the small print at the end).

Before you contribute

Before we can use your code, you must sign the
Google Individual Contributor License Agreement
(CLA), which you can do online. The CLA is necessary mainly because you own the
copyright to your changes, even after your contribution becomes part of our
codebase, so we need your permission to use and distribute your code. We also
need to be sure of various other thingsβ€”for instance that you'll tell us if you
know that your code infringes on other people's patents. You don't have to sign
the CLA until after you've submitted your code for review and a member has
approved it, but you must do it before we can put your code into our codebase.
Before you start working on a larger contribution, you should get in touch with
us first through the issue tracker with your idea so that we can help out and
possibly guide you. Coordinating up front makes it much easier to avoid
frustration later on.

Code reviews

All submissions, including submissions by project members, require review. We
use Github pull requests for this purpose.

The small print

Contributions made by corporations are covered by a different agreement than
the one above, the
Software Grant and Corporate Contributor License Agreement.