Result for 752087774DC1B9D79087BB245BF2D35ED7842606

Query result

Key Value
FileName./usr/share/man/man3/Test::Roo::Class.3pm.gz
FileSize2117
MD53511FAE2E0AD584C8643880970CB65EC
SHA-1752087774DC1B9D79087BB245BF2D35ED7842606
SHA-256EE6A2E3ED168EAA7B8CC19895A59002220524218D03068034869629477A3D54C
SSDEEP48:XnO8iLBOh8MGiszBMGkQUqpOs6C/VXoNDJ9V8Czyo02Ic:3u4qt9MG0q8soNDJL7yo/
TLSHT19B414CB56FAC36F65117E0EB120FE4007B9B1EF7C8E1C82E9059C0B48CE219B5A43A4C
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileSize29896
MD51B66BB7ECCCCC7B5FB4B6CCB064C7EFC
PackageDescriptionmodule 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamelibtest-roo-perl
PackageSectionperl
PackageVersion1.004-1.1
SHA-17AF6B858697E7118881E998B6A4B742C52A4A76F
SHA-256DE29F5F15BD4943DD7DAFECD015EA527EDB4260E4FB74C16D2B179BCF9812B45
Key Value
FileSize30816
MD57806E3E9195B1ED9B0EDD9DAEFAF1D79
PackageDescriptionmodule 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.
PackageMaintainerDebian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
PackageNamelibtest-roo-perl
PackageSectionperl
PackageVersion1.004-1.1
SHA-16FBB544F484A3F8F857E87BAAD3D8CB019E6C433
SHA-25660438E4FE73F5F0C2CAB4F553721728ED43709D7B931AF947839B4A6E51F532F