How to Install and Uninstall perl-Test-Kit Package on openSuSE Tumbleweed
Last updated: November 23,2024
1. Install "perl-Test-Kit" package
Please follow the instructions below to install perl-Test-Kit on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
perl-Test-Kit
Copied
2. Uninstall "perl-Test-Kit" package
Please follow the guidance below to uninstall perl-Test-Kit on openSuSE Tumbleweed:
$
sudo zypper remove
perl-Test-Kit
Copied
3. Information about the perl-Test-Kit package on openSuSE Tumbleweed
Information for package perl-Test-Kit:
--------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : perl-Test-Kit
Version : 2.160.0-2.1
Arch : noarch
Vendor : openSUSE
Installed Size : 35.3 KiB
Installed : No
Status : not installed
Source package : perl-Test-Kit-2.160.0-2.1.src
Upstream URL : https://metacpan.org/release/Test-Kit
Summary : Build custom test packages with only the features you want
Description :
Test::Kit allows you to create a single module in your project which gives
you access to all of the testing functions you want.
Its primary goal is to reduce boilerplate code that is currently littering
the top of all your test files.
It also allows your testing to be more consistent; for example it becomes a
trivial change to include Test::FailWarnings in all of your tests, and
there is no danger that you forget to include it in a new test.
--------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : perl-Test-Kit
Version : 2.160.0-2.1
Arch : noarch
Vendor : openSUSE
Installed Size : 35.3 KiB
Installed : No
Status : not installed
Source package : perl-Test-Kit-2.160.0-2.1.src
Upstream URL : https://metacpan.org/release/Test-Kit
Summary : Build custom test packages with only the features you want
Description :
Test::Kit allows you to create a single module in your project which gives
you access to all of the testing functions you want.
Its primary goal is to reduce boilerplate code that is currently littering
the top of all your test files.
It also allows your testing to be more consistent; for example it becomes a
trivial change to include Test::FailWarnings in all of your tests, and
there is no danger that you forget to include it in a new test.