Covered uses modern Ruby features to generate comprehensive coverage, including support for templates which are compiled into Ruby.
- Incremental coverage - if you run your full test suite, and the run a subset, it will still report the correct coverage - so you can incrementally work on improving coverage.
- Integration with Sus, Git, RSpec and Minitest- no need to configure anything - out of the box support for these platforms.
- Supports coverage of views - templates compiled to Ruby code can be tracked for coverage reporting.
Originally, Ruby coverage tools were unable to handle evaled code. This is because the coverage module built into
Ruby doesn't expose the necessary hooks to capture it. Using the parser gem and
trace points allows us to do our own source code analysis to compute executable lines, thus making it possible to
compute coverage for "templates".
After this concept prooved useful, it was integrated directly into Ruby.
Please see the project documentation for more details.
-
Getting Started - This guide explains how to get started with
coveredand integrate it with your test suite. -
Configuration - This guide will help you to configure covered for your project's specific requirements.
- simplecov – one of the original coverage implementations for Ruby, uses
the built-in
coveragelibrary. - sus - a test framework which uses
coveredto generate coverage reports.
We welcome contributions to this project.
- Fork it.
- Create your feature branch (
git checkout -b my-new-feature). - Commit your changes (
git commit -am 'Add some feature'). - Push to the branch (
git push origin my-new-feature). - Create new Pull Request.
This project uses the Developer Certificate of Origin. All contributors to this project must agree to this document to have their contributions accepted.
This project is governed by the Contributor Covenant. All contributors and participants agree to abide by its terms.