How to Install and Uninstall libtest-roo-perl Package on Kali Linux
Last updated: January 22,2025
1. Install "libtest-roo-perl" package
This tutorial shows how to install libtest-roo-perl on Kali Linux
$
sudo apt update
Copied
$
sudo apt install
libtest-roo-perl
Copied
2. Uninstall "libtest-roo-perl" package
In this section, we are going to explain the necessary steps to uninstall libtest-roo-perl on Kali Linux:
$
sudo apt remove
libtest-roo-perl
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the libtest-roo-perl package on Kali Linux
Package: libtest-roo-perl
Version: 1.004-2
Installed-Size: 95
Maintainer: Debian Perl Group
Architecture: all
Depends: perl:any, libmoo-perl, libmoox-types-mooselike-perl, libstrictures-perl, libsub-install-perl, perl | libtest-simple-perl
Recommends: libbareword-filehandles-perl, libindirect-perl, libmultidimensional-perl
Size: 31128
SHA256: 98fc5ab96931c247bfe5395270d739561b320de7b9ea72010a2edba688ce989b
SHA1: 693d630173d4eec722b9e39d9fe8f0e3fa42bc3c
MD5sum: 629f4e3f9d447ce0f044fb4d9252a43f
Description: module for composable, reusable tests with roles and Moo
Test::Roo allows you to compose Test::More tests from roles. It is inspired
by the excellent Test::Routine module, but uses Moo instead of Moose. This
gives most of the benefits without the need for Moose as a test dependency.
.
Test files are Moo classes. You can define any needed test fixtures as Moo
attributes. You define tests as method modifiers -- similar in concept to
"subtest" in Test::More, but your test method will be passed the test object
for access to fixture attributes. You may compose any Moo::Role into your
test to define attributes, require particular methods, or define tests.
.
This means that you can isolate test *behaviors* into roles which require
certain test *fixtures* in order to run. Your main test file will provide the
fixtures and compose the roles to run. This makes it easy to reuse test
behaviors.
.
For example, if you are creating tests for Awesome::Module, you could create
the test behaviors as Awesome::Module::Test::Role and distribute it with your
module. If another distribution subclasses Awesome::Module, it can compose
the Awesome::Module::Test::Role behavior for its own tests.
.
No more copying and pasting tests from a super class! Superclasses define and
share their tests. Subclasses provide their own fixtures and run the tests.
Description-md5:
Homepage: https://metacpan.org/release/Test-Roo
Tag: devel::lang:perl, devel::library, implemented-in::perl
Section: perl
Priority: optional
Filename: pool/main/libt/libtest-roo-perl/libtest-roo-perl_1.004-2_all.deb
Version: 1.004-2
Installed-Size: 95
Maintainer: Debian Perl Group
Architecture: all
Depends: perl:any, libmoo-perl, libmoox-types-mooselike-perl, libstrictures-perl, libsub-install-perl, perl | libtest-simple-perl
Recommends: libbareword-filehandles-perl, libindirect-perl, libmultidimensional-perl
Size: 31128
SHA256: 98fc5ab96931c247bfe5395270d739561b320de7b9ea72010a2edba688ce989b
SHA1: 693d630173d4eec722b9e39d9fe8f0e3fa42bc3c
MD5sum: 629f4e3f9d447ce0f044fb4d9252a43f
Description: module for composable, reusable tests with roles and Moo
Test::Roo allows you to compose Test::More tests from roles. It is inspired
by the excellent Test::Routine module, but uses Moo instead of Moose. This
gives most of the benefits without the need for Moose as a test dependency.
.
Test files are Moo classes. You can define any needed test fixtures as Moo
attributes. You define tests as method modifiers -- similar in concept to
"subtest" in Test::More, but your test method will be passed the test object
for access to fixture attributes. You may compose any Moo::Role into your
test to define attributes, require particular methods, or define tests.
.
This means that you can isolate test *behaviors* into roles which require
certain test *fixtures* in order to run. Your main test file will provide the
fixtures and compose the roles to run. This makes it easy to reuse test
behaviors.
.
For example, if you are creating tests for Awesome::Module, you could create
the test behaviors as Awesome::Module::Test::Role and distribute it with your
module. If another distribution subclasses Awesome::Module, it can compose
the Awesome::Module::Test::Role behavior for its own tests.
.
No more copying and pasting tests from a super class! Superclasses define and
share their tests. Subclasses provide their own fixtures and run the tests.
Description-md5:
Homepage: https://metacpan.org/release/Test-Roo
Tag: devel::lang:perl, devel::library, implemented-in::perl
Section: perl
Priority: optional
Filename: pool/main/libt/libtest-roo-perl/libtest-roo-perl_1.004-2_all.deb