Result for 2792D5CCEA69F8E6EA02639146CE06F758EBA216

Query result

Key Value
FileName./usr/share/doc/perl-Test-Roo/Changes
FileSize1844
MD5E5BCE107F61B50DFE25C4A28DFC2BE93
SHA-12792D5CCEA69F8E6EA02639146CE06F758EBA216
SHA-25625DA55BED19C1044D35ECF84F3668C155D59FBE05C184732ADE3C1727C2FBF31
SSDEEP24:cwvDxRppFidNBurwodlyly76UxY8BMI3U6/zNyz2ZFyB1xEkxEKh0G6oqzSHM6Xh:ccXpidOsgxr/HG8+50muMv
TLSHT17831E312A76A229477D642C765C4A2D47534F13FD68B2968BAFC009C9F47060B36B89D
hashlookup:parent-total17
hashlookup:trust100

Network graph view

Parents (Total: 17)

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

Key Value
MD569F33A6D9D2FAEF31F357DFB3FC3DFF2
PackageArchnoarch
PackageDescriptionThis module allows you to compose the Test::More manpage tests from roles. It is inspired by the excellent the Test::Routine manpage module, but uses the Moo manpage instead of the Moose manpage. This gives most of the benefits without the need for the Moose manpage 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 the Test::More manpage, but your test method will be passed the test object for access to fixture attributes. You may compose any the Moo::Role manpage 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.
PackageMaintainerumeabot <umeabot>
PackageNameperl-Test-Roo
PackageRelease6.mga7
PackageVersion1.4.0
SHA-10D973CCCE8592E5E401F5C5B25811AD221A80B26
SHA-25671A53812604254908DABBE1A630211CB272DA60225D17B927F53F96B6E5B0C4F
Key Value
MD5159FD51355BA04D60E78953972F68DB6
PackageArchnoarch
PackageDescriptionThis module allows you to compose the Test::More manpage tests from roles. It is inspired by the excellent the Test::Routine manpage module, but uses the Moo manpage instead of the Moose manpage. This gives most of the benefits without the need for the Moose manpage 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 the Test::More manpage, but your test method will be passed the test object for access to fixture attributes. You may compose any the Moo::Role manpage 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.
PackageMaintainerumeabot <umeabot>
PackageNameperl-Test-Roo
PackageRelease7.mga8
PackageVersion1.4.0
SHA-1133E4CCA98D2AD8A0398311EC3360BC022843CA7
SHA-256B03D6EE9ED9EE64D24BDA4E6E6FE7C6B3E808E7ED4F9880387F5E93C8FCCA534
Key Value
MD5FECD79331D65A61B1D900A3923880552
PackageArchnoarch
PackageDescriptionThis 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.
PackageNameperl-Test-Roo
PackageRelease1.10
PackageVersion1.004
SHA-12C58CD28334C1E5307E1F44CB6F36F1B1594A021
SHA-256351620E38022D9DE02BED5ECC340CE5B3255664527B2EEE2E36CD388A60F3815
Key Value
MD526B682B5BADAE9B1E09C0788027CA78B
PackageArchnoarch
PackageDescriptionThis module allows you to compose the Test::More manpage tests from roles. It is inspired by the excellent the Test::Routine manpage module, but uses the Moo manpage instead of the Moose manpage. This gives most of the benefits without the need for the Moose manpage 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 the Test::More manpage, but your test method will be passed the test object for access to fixture attributes. You may compose any the Moo::Role manpage 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.
PackageNameperl-Test-Roo
PackageRelease1.49
PackageVersion1.004
SHA-13A14C7482965F0F1A7104C415F15FC46D9D384EC
SHA-256DEA2AE227463BB87B1535A5123375CDBE922820E8E6F308B21FD5888DF6DB524
Key Value
MD5E8ACF661BB558194356A5AF8596F8CCB
PackageArchnoarch
PackageDescriptionThis 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.
PackageNameperl-Test-Roo
PackageRelease1.62
PackageVersion1.004
SHA-13A6436003F1CB6877EDD592B736CB95F69509FBF
SHA-25605126C1E738121F1B0A49A501B1B15D50DBAEC4F79907EAD0C1E2136C471587A
Key Value
MD5D5E7A960ADA92AF8F547D1C213100C48
PackageArchnoarch
PackageDescriptionThis 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.
PackageNameperl-Test-Roo
PackageRelease1.5
PackageVersion1.004
SHA-141DFBD2D3028466B310C9D4372FAAF93E883E0DD
SHA-2563F2BF594299078544983AED373F945F9D2078A1AAAD2A749C58B0D3BD01F750C
Key Value
MD5BCFE70138355A62AFD9E9CF76D99FFB2
PackageArchnoarch
PackageDescriptionThis 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.
PackageNameperl-Test-Roo
PackageRelease1.4
PackageVersion1.004
SHA-15274783EB4DCFF4A6921CC92AAEDB1325C0406A7
SHA-256B400262694A7E69BF903AE019143A43B53FC38208EBC846F8AB3FB87E26AAA1C
Key Value
MD580A94A17D780DCD6C88C31F26426827B
PackageArchnoarch
PackageDescriptionThis module allows you to compose the Test::More manpage tests from roles. It is inspired by the excellent the Test::Routine manpage module, but uses the Moo manpage instead of the Moose manpage. This gives most of the benefits without the need for the Moose manpage 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 the Test::More manpage, but your test method will be passed the test object for access to fixture attributes. You may compose any the Moo::Role manpage 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.
PackageMaintainerumeabot <umeabot>
PackageNameperl-Test-Roo
PackageRelease8.mga9
PackageVersion1.4.0
SHA-15E30D35AC4AF398EF21FE0C79829193B58BFF72B
SHA-256DF878E90B65B8CD38668A9A9E9C71D6356DAFA23B0D24489D915393CF6DF3B15
Key Value
MD5DC739FBE80C5EE8264EB6B1389105638
PackageArchnoarch
PackageDescriptionThis 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.
PackageMaintainerFedora Project
PackageNameperl-Test-Roo
PackageRelease15.fc33
PackageVersion1.004
SHA-15E85B40E82A23B1F611A446949D8E157E2778670
SHA-25682A83A43720ABD7637DE026FB77AE157C3A37E59070878FEF3D24A62805A3A48
Key Value
MD58DF5DDEAB5A105A1ECCC7661C5F66696
PackageArchnoarch
PackageDescriptionThis 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.
PackageNameperl-Test-Roo
PackageReleaselp152.1.1
PackageVersion1.004
SHA-16342D804DB1CE365165BFFDC332EC85BEECB1C57
SHA-256A19BFF84D9791D8C265838A454C410E9A86A195AA3B841A351BF4BAA6461D9BB