Result for 09A295648BE860CB7598BD5735645302CEBE3FEC

Query result

Key Value
FileName./usr/share/doc/libtest-roo-perl/changelog.Debian.gz
FileSize413
MD51B2B5BDC1C7AC74B7590584C73E7AD7B
SHA-109A295648BE860CB7598BD5735645302CEBE3FEC
SHA-25600F967120C2E8500EBF3B28F22066DE89CCA620676B74AD0A095AA5C84981AFF
SSDEEP6:XtotO6245Ir0SAYX+35khV9cBfniEUM2iGIFERtaP1PdnL9TZJxzg7wMAZBeMasN:XWt9qOb5kPgfiC2iUMd7LwNKANXu
TLSHT1B5E0F182E2EA0AA3F98213B4E590C29C90F6627147B744C824D04A3C65EF25BF04C3D9
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