All Projects → pjcj → Devel Cover

pjcj / Devel Cover

Code coverage metrics for Perl

Programming Languages

perl
6916 projects

Projects that are alternatives of or similar to Devel Cover

Alsatian
TypeScript testing framework with test cases
Stars: ✭ 244 (+168.13%)
Mutual labels:  test, coverage
jest-it-up
🌐📈 Automatically bump up global Jest thresholds whenever coverage goes above them
Stars: ✭ 37 (-59.34%)
Mutual labels:  coverage, test
cover.run
Code coverage
Stars: ✭ 34 (-62.64%)
Mutual labels:  coverage, test
Axocover
Nice and free .Net code coverage support for Visual Studio with OpenCover.
Stars: ✭ 237 (+160.44%)
Mutual labels:  coverage, code
pytest-coverage-comment
Comments a pull request with the pytest code coverage badge and full report
Stars: ✭ 32 (-64.84%)
Mutual labels:  coverage, test
angular-cli-skeleton
angular-cli skeleton to quickly start a new project with advanced features and best practices. All features are described in README.md.
Stars: ✭ 32 (-64.84%)
Mutual labels:  coverage, test
eaf-linter
🤪 A linter, prettier, and test suite that does everything as-simple-as-possible.
Stars: ✭ 17 (-81.32%)
Mutual labels:  code, test
kotlin-plugin-generated
A Kotlin compiler plugin that annotates Kotlin-generated methods for improved coverage reports
Stars: ✭ 33 (-63.74%)
Mutual labels:  coverage, test
goverage
go test -coverprofile for multiple packages
Stars: ✭ 87 (-4.4%)
Mutual labels:  coverage, test
goverreport
Command line tool for coverage reporting and validation
Stars: ✭ 44 (-51.65%)
Mutual labels:  coverage, test
Gogradle
A Gradle Plugin Providing Full Support for Go
Stars: ✭ 712 (+682.42%)
Mutual labels:  test, coverage
Shellspec
A full-featured BDD unit testing framework for bash, ksh, zsh, dash and all POSIX shells
Stars: ✭ 375 (+312.09%)
Mutual labels:  test, coverage
Kahlan
✔️ PHP Test Framework for Freedom, Truth, and Justice
Stars: ✭ 1,065 (+1070.33%)
Mutual labels:  test, coverage
Opencover
A code coverage tool for .NET 2 and above (WINDOWS OS only), support for 32 and 64 processes with both branch and sequence points
Stars: ✭ 1,256 (+1280.22%)
Mutual labels:  coverage
Swagger Coverage
Tool which generates full picture of coverage of API tests based on OAS 2 (Swagger)
Stars: ✭ 89 (-2.2%)
Mutual labels:  coverage
Ribstreeviewerclient
Real Time viewing attached RIBs Tree on Browser
Stars: ✭ 84 (-7.69%)
Mutual labels:  test
Dspot
Automatically detect and generate missing assertions for Junit test cases (also known as test amplification)
Stars: ✭ 83 (-8.79%)
Mutual labels:  coverage
App Test Arch
Android 单元测试、Monkey、LeakCanary测试demo项目【粗略示例】
Stars: ✭ 90 (-1.1%)
Mutual labels:  test
Scalatestplus Play
ScalaTest + Play
Stars: ✭ 88 (-3.3%)
Mutual labels:  test
Re Frame Test
Cross platform (cljs and clj) utilities for testing re-frame applications
Stars: ✭ 83 (-8.79%)
Mutual labels:  test

Devel::Cover

Code coverage metrics for Perl

This module provides code coverage metrics for Perl. Code coverage metrics describe how thoroughly tests exercise code. By using Devel::Cover you can discover areas of code not exercised by your tests and determine which tests to create to increase coverage. Code coverage can be considered an indirect measure of quality.

Although it is still being developed, Devel::Cover is now quite stable and provides many of the features to be expected in a useful coverage tool.

Statement, branch, condition, subroutine, and pod coverage information is reported. Statement and subroutine coverage data should be accurate. Branch and condition coverage data should be mostly accurate too, although not always what one might initially expect. Pod coverage comes from Pod::Coverage. If Pod::Coverage::CountParents is available it will be used instead. Coverage data for other criteria are not yet collected.

The cover program can be used to generate coverage reports. Devel::Cover ships with a number of reports including various types of HTML output, textual reports, a report to display missing coverage in the same format as compilation errors and a report to display coverage information within the Vim editor.

It is possible to add annotations to reports, for example you can add a column to an HTML report showing who last changed a line, as determined by git blame. Some annotation modules are shipped with Devel::Cover and you can easily create your own.

The gcov2perl program can be used to convert gcov files to "Devel::Cover" databases. This allows you to display your C or XS code coverage together with your Perl coverage, or to use any of the Devel::Cover reports to display your C coverage data.

Code coverage data are collected by replacing perl ops with functions which count how many times the ops are executed. These data are then mapped back to reality using the B compiler modules. There is also a statement profiling facility which should not be relied on. For proper profiling use Devel::NYTProf. Previous versions of Devel::Cover collected coverage data by replacing perl's runops function. It is still possible to switch to that mode of operation, but this now gets little testing and will probably be removed soon. You probably don't care about any of this.

The most appropriate mailing list on which to discuss this module would be perl-qa. See http://lists.perl.org/list/perl-qa.html.

The Devel::Cover repository can be found at http://github.com/pjcj/Devel--Cover. This is also where problems should be reported.

To get coverage for an uninstalled module:

cover -test

or

cover -delete
HARNESS_PERL_SWITCHES=-MDevel::Cover make test
cover

To get coverage for an uninstalled module which uses Module::Build (0.26 or later):

./Build testcover

If the module does not use the t/*.t framework:

PERL5OPT=-MDevel::Cover make test

If you want to get coverage for a program:

perl -MDevel::Cover yourprog args
cover

To alter default values:

perl -MDevel::Cover=-db,cover_db,-coverage,statement,time yourprog args
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].