Parents (Total: 9)

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

Key	Value
MD5	D5E7A960ADA92AF8F547D1C213100C48
PackageArch	noarch
PackageDescription	This module 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.
PackageName	perl-Test-Roo
PackageRelease	1.5
PackageVersion	1.004
SHA-1	41DFBD2D3028466B310C9D4372FAAF93E883E0DD
SHA-256	3F2BF594299078544983AED373F945F9D2078A1AAAD2A749C58B0D3BD01F750C

Key	Value
MD5	543F8E5F47E6F2744C62FB082D2B10A6
PackageArch	noarch
PackageDescription	This module 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.
PackageName	perl-Test-Roo
PackageRelease	lp153.1.9
PackageVersion	1.004
SHA-1	E28ED621DB06C7B11A361CBC217CD299BF5599E6
SHA-256	F44695B3C4C8A3F2D73249F0612CFA6C462329A3981D368A80E2CEBFA3E71E19

Key	Value
MD5	BC1FB05548008BF870EE97C549AF3BF5
PackageArch	noarch
PackageDescription	This module 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.
PackageName	perl-Test-Roo
PackageRelease	lp151.1.1
PackageVersion	1.004
SHA-1	F9530DE5E5052622A94BF4539D9B6F3FAF34BF44
SHA-256	81065EC6D5A2DE53072C434508B1FCA12AB150AEB8C49108366AA3EAAE036B3D

Key	Value
MD5	30A91C058F84F2B75D6F8C0F72E4773D
PackageArch	noarch
PackageDescription	This module 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.
PackageName	perl-Test-Roo
PackageRelease	lp150.1.2
PackageVersion	1.004
SHA-1	D8A44B5BC2BDD4A6D8138F24A381C61B66A8669D
SHA-256	5B0C9A35098C3CDF5F2E70EBA90EC1A14D12AE0036CE1B6A39B2F129A120AC54

Key	Value
MD5	6B0B20D4A611581622A759C296FAE7F3
PackageArch	noarch
PackageDescription	This module 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.
PackageName	perl-Test-Roo
PackageRelease	1.1
PackageVersion	1.004
SHA-1	ECBA417F54A4ACF1965A91ABC5C548C1776FB61D
SHA-256	91F8B474C93368A3687737E7C36593E820B3592C7A58559C84D8F29388992CC7

Key	Value
MD5	BCFE70138355A62AFD9E9CF76D99FFB2
PackageArch	noarch
PackageDescription	This module 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.
PackageName	perl-Test-Roo
PackageRelease	1.4
PackageVersion	1.004
SHA-1	5274783EB4DCFF4A6921CC92AAEDB1325C0406A7
SHA-256	B400262694A7E69BF903AE019143A43B53FC38208EBC846F8AB3FB87E26AAA1C

Key	Value
MD5	18F6D15309EF83E54E7D402625931168
PackageArch	noarch
PackageDescription	This module 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.
PackageName	perl-Test-Roo
PackageRelease	1.2
PackageVersion	1.004
SHA-1	660B6297E14D4E51B62F50D569D17D4EF0097F79
SHA-256	601773CB289DF7FC937018494B1F1E4CE642543AFF51963272FDD1BF2A49A853

Key	Value
MD5	8DF5DDEAB5A105A1ECCC7661C5F66696
PackageArch	noarch
PackageDescription	This module 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.
PackageName	perl-Test-Roo
PackageRelease	lp152.1.1
PackageVersion	1.004
SHA-1	6342D804DB1CE365165BFFDC332EC85BEECB1C57
SHA-256	A19BFF84D9791D8C265838A454C410E9A86A195AA3B841A351BF4BAA6461D9BB

Key	Value
MD5	FECD79331D65A61B1D900A3923880552
PackageArch	noarch
PackageDescription	This module 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.
PackageName	perl-Test-Roo
PackageRelease	1.10
PackageVersion	1.004
SHA-1	2C58CD28334C1E5307E1F44CB6F36F1B1594A021
SHA-256	351620E38022D9DE02BED5ECC340CE5B3255664527B2EEE2E36CD388A60F3815