How to Install and Uninstall perl-Devel-Cover Package on openSuSE Tumbleweed

Last updated: July 04,2024

1. Install "perl-Devel-Cover" package

This is a short guide on how to install perl-Devel-Cover on openSuSE Tumbleweed

$ sudo zypper refresh $ sudo zypper install perl-Devel-Cover

2. Uninstall "perl-Devel-Cover" package

This guide covers the steps necessary to uninstall perl-Devel-Cover on openSuSE Tumbleweed:

$ sudo zypper remove perl-Devel-Cover

3. Information about the perl-Devel-Cover package on openSuSE Tumbleweed

Information for package perl-Devel-Cover:
-----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : perl-Devel-Cover
Version : 1.40-1.5
Arch : x86_64
Vendor : openSUSE
Installed Size : 576.2 KiB
Installed : No
Status : not installed
Source package : perl-Devel-Cover-1.40-1.5.src
Upstream URL : https://metacpan.org/release/Devel-Cover
Summary : Code coverage metrics for Perl
Description :
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.
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.
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.