Key | Value |
---|---|
FileName | ./usr/share/man/man3/App::Prove::Plugin::HTML.3pm.gz |
FileSize | 2870 |
MD5 | FD2936458EC85C29C5CFB97586994304 |
SHA-1 | 452C4E60CC33F8F286ECAE29BFCF7DD7EB10CF8D |
SHA-256 | 477376286B08DADE9BF9C3F07999766EAEF1DE7856969FEF245F70B2A942A3C1 |
SSDEEP | 48:XG9VeCZg7/E3n2fD8kw46sAGHBwxVVmHzEq/P4GlZnGtPaxGybO31e1HBfx6THxb:27eSiYB32OV4HzdX4snGM0ybO24yef |
TLSH | T143512A568B177113A53FB97E373E39165D907A0881CD0D4C290BF9184D3C7282A67609 |
hashlookup:parent-total | 7 |
hashlookup:trust | 85 |
The searched file hash is included in 7 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | F2ACD4D688C776D7718DD4BD8DB8588B |
PackageArch | noarch |
PackageDescription | This module provides HTML output formatting for the TAP::Harness manpage (a replacement for the Test::Harness manpage. It is largely based on ideas from the TAP::Test::HTMLMatrix manpage (which was built on the Test::Harness manpage and thus had a few limitations - hence this module). For sample output, see: the http://www.spurkis.org/TAP-Formatter-HTML/test-output.html manpage This module is targeted at all users of automated test suites. It's meant to make reading test results easier, giving you a visual summary of your test suite and letting you drill down into individual failures (which will hopefully make testing more likely to happen at your organization ;-). The design goals are: * * _easy to use_ Once you've got your test report, it should be obvious how to use it. * * _helpful_ It should be helpful by pointing out _where_ & _why_ your test suite is breaking. If you've written your tests well, it should give you enough info to start tracking down the issue. * * _easy to install_ Eg: should be a clean install from CPAN, and you shouldn't need to modify your existing test suite to get up & running, though _you will need to stop using the Test::Harness manpage unfortunately_. * * _work out of the box_ You shouldn't need to do any custom-coding to get it working - the default configuration & templates should be enough to get started with. Once installed it should be a matter of running: % prove -m -Q --formatter=TAP::Formatter::HTML >output.html From your project's home dir, and opening the resulting file. * * _easy to configure_ You should be able to configure & customize it to suit your needs. As such, css, javascript and templates are all configurable. |
PackageName | perl-TAP-Formatter-HTML |
PackageRelease | lp151.1.1 |
PackageVersion | 0.11 |
SHA-1 | 6826B39EAC4884FC097AD9CF734760BBAFB68FA5 |
SHA-256 | 30623A04AF6E6F7941BF8A2677667EB67F3E3C96B2329EE664B1D1A6DC193B53 |
Key | Value |
---|---|
MD5 | 0C085AC431F66A361C4435179E44E41B |
PackageArch | noarch |
PackageDescription | This module provides HTML output formatting for the TAP::Harness manpage (a replacement for the Test::Harness manpage. It is largely based on ideas from the TAP::Test::HTMLMatrix manpage (which was built on the Test::Harness manpage and thus had a few limitations - hence this module). For sample output, see: the http://www.spurkis.org/TAP-Formatter-HTML/test-output.html manpage This module is targeted at all users of automated test suites. It's meant to make reading test results easier, giving you a visual summary of your test suite and letting you drill down into individual failures (which will hopefully make testing more likely to happen at your organization ;-). The design goals are: * * _easy to use_ Once you've got your test report, it should be obvious how to use it. * * _helpful_ It should be helpful by pointing out _where_ & _why_ your test suite is breaking. If you've written your tests well, it should give you enough info to start tracking down the issue. * * _easy to install_ Eg: should be a clean install from CPAN, and you shouldn't need to modify your existing test suite to get up & running, though _you will need to stop using the Test::Harness manpage unfortunately_. * * _work out of the box_ You shouldn't need to do any custom-coding to get it working - the default configuration & templates should be enough to get started with. Once installed it should be a matter of running: % prove -m -Q --formatter=TAP::Formatter::HTML >output.html From your project's home dir, and opening the resulting file. * * _easy to configure_ You should be able to configure & customize it to suit your needs. As such, css, javascript and templates are all configurable. |
PackageName | perl-TAP-Formatter-HTML |
PackageRelease | lp150.1.2 |
PackageVersion | 0.11 |
SHA-1 | AB99A55D2C334B21421D10ED161239536519060F |
SHA-256 | 9F621E64FEAFF31CFD8EDFFCC252068121795305EDB02B7080D0218C8797F0F1 |
Key | Value |
---|---|
MD5 | 50A432174383F07BD5AA19A47DA75D09 |
PackageArch | noarch |
PackageDescription | This module provides HTML output formatting for the TAP::Harness manpage (a replacement for the Test::Harness manpage. It is largely based on ideas from the TAP::Test::HTMLMatrix manpage (which was built on the Test::Harness manpage and thus had a few limitations - hence this module). For sample output, see: the http://www.spurkis.org/TAP-Formatter-HTML/test-output.html manpage This module is targeted at all users of automated test suites. It's meant to make reading test results easier, giving you a visual summary of your test suite and letting you drill down into individual failures (which will hopefully make testing more likely to happen at your organization ;-). The design goals are: * * _easy to use_ Once you've got your test report, it should be obvious how to use it. * * _helpful_ It should be helpful by pointing out _where_ & _why_ your test suite is breaking. If you've written your tests well, it should give you enough info to start tracking down the issue. * * _easy to install_ Eg: should be a clean install from CPAN, and you shouldn't need to modify your existing test suite to get up & running, though _you will need to stop using the Test::Harness manpage unfortunately_. * * _work out of the box_ You shouldn't need to do any custom-coding to get it working - the default configuration & templates should be enough to get started with. Once installed it should be a matter of running: % prove -m -Q --formatter=TAP::Formatter::HTML >output.html From your project's home dir, and opening the resulting file. * * _easy to configure_ You should be able to configure & customize it to suit your needs. As such, css, javascript and templates are all configurable. |
PackageName | perl-TAP-Formatter-HTML |
PackageRelease | lp152.3.1 |
PackageVersion | 0.11 |
SHA-1 | 1FD3136334747C9A55E5083D50FE8ABB57C59A22 |
SHA-256 | 5D068E25D37998BD1439EA6157B3B71567EE665861041FDC39E10C8969A0CB3D |
Key | Value |
---|---|
MD5 | 0C4216722AA7ACCBB17BA751785E186A |
PackageArch | noarch |
PackageDescription | This module provides HTML output formatting for the TAP::Harness manpage (a replacement for the Test::Harness manpage. It is largely based on ideas from the TAP::Test::HTMLMatrix manpage (which was built on the Test::Harness manpage and thus had a few limitations - hence this module). For sample output, see: the http://www.spurkis.org/TAP-Formatter-HTML/test-output.html manpage This module is targeted at all users of automated test suites. It's meant to make reading test results easier, giving you a visual summary of your test suite and letting you drill down into individual failures (which will hopefully make testing more likely to happen at your organization ;-). The design goals are: * * _easy to use_ Once you've got your test report, it should be obvious how to use it. * * _helpful_ It should be helpful by pointing out _where_ & _why_ your test suite is breaking. If you've written your tests well, it should give you enough info to start tracking down the issue. * * _easy to install_ Eg: should be a clean install from CPAN, and you shouldn't need to modify your existing test suite to get up & running, though _you will need to stop using the Test::Harness manpage unfortunately_. * * _work out of the box_ You shouldn't need to do any custom-coding to get it working - the default configuration & templates should be enough to get started with. Once installed it should be a matter of running: % prove -m -Q --formatter=TAP::Formatter::HTML >output.html From your project's home dir, and opening the resulting file. * * _easy to configure_ You should be able to configure & customize it to suit your needs. As such, css, javascript and templates are all configurable. |
PackageName | perl-TAP-Formatter-HTML |
PackageRelease | 1.23 |
PackageVersion | 0.11 |
SHA-1 | F2FB05B4F31AE4C2DD31C72A940061F0E18AF34A |
SHA-256 | 9287055BBFE780CC6496F61646E6F8348DA446B3593DBACDA7DB6AD52B82FB6A |
Key | Value |
---|---|
MD5 | 16F876DD1DCC00D29735D9386464CE01 |
PackageArch | noarch |
PackageDescription | This module provides HTML output formatting for the TAP::Harness manpage (a replacement for the Test::Harness manpage. It is largely based on ideas from the TAP::Test::HTMLMatrix manpage (which was built on the Test::Harness manpage and thus had a few limitations - hence this module). For sample output, see: the http://www.spurkis.org/TAP-Formatter-HTML/test-output.html manpage This module is targeted at all users of automated test suites. It's meant to make reading test results easier, giving you a visual summary of your test suite and letting you drill down into individual failures (which will hopefully make testing more likely to happen at your organization ;-). The design goals are: * * _easy to use_ Once you've got your test report, it should be obvious how to use it. * * _helpful_ It should be helpful by pointing out _where_ & _why_ your test suite is breaking. If you've written your tests well, it should give you enough info to start tracking down the issue. * * _easy to install_ Eg: should be a clean install from CPAN, and you shouldn't need to modify your existing test suite to get up & running, though _you will need to stop using the Test::Harness manpage unfortunately_. * * _work out of the box_ You shouldn't need to do any custom-coding to get it working - the default configuration & templates should be enough to get started with. Once installed it should be a matter of running: % prove -m -Q --formatter=TAP::Formatter::HTML >output.html From your project's home dir, and opening the resulting file. * * _easy to configure_ You should be able to configure & customize it to suit your needs. As such, css, javascript and templates are all configurable. |
PackageName | perl-TAP-Formatter-HTML |
PackageRelease | lp153.1.1 |
PackageVersion | 0.11 |
SHA-1 | 98B4B8CBA98D7A58D79A62ED0A6A54A4EF08739C |
SHA-256 | D5D3A7F340C4DFE5BA624CC5DC852AF660931F8E6734AD7C2B333F81E3E89FCB |
Key | Value |
---|---|
MD5 | 028E48BCC7AF7F10F53E0920D8769CA1 |
PackageArch | noarch |
PackageDescription | This module provides HTML output formatting for the TAP::Harness manpage (a replacement for the Test::Harness manpage. It is largely based on ideas from the TAP::Test::HTMLMatrix manpage (which was built on the Test::Harness manpage and thus had a few limitations - hence this module). For sample output, see: the http://www.spurkis.org/TAP-Formatter-HTML/test-output.html manpage This module is targeted at all users of automated test suites. It's meant to make reading test results easier, giving you a visual summary of your test suite and letting you drill down into individual failures (which will hopefully make testing more likely to happen at your organization ;-). The design goals are: * * _easy to use_ Once you've got your test report, it should be obvious how to use it. * * _helpful_ It should be helpful by pointing out _where_ & _why_ your test suite is breaking. If you've written your tests well, it should give you enough info to start tracking down the issue. * * _easy to install_ Eg: should be a clean install from CPAN, and you shouldn't need to modify your existing test suite to get up & running, though _you will need to stop using the Test::Harness manpage unfortunately_. * * _work out of the box_ You shouldn't need to do any custom-coding to get it working - the default configuration & templates should be enough to get started with. Once installed it should be a matter of running: % prove -m -Q --formatter=TAP::Formatter::HTML >output.html From your project's home dir, and opening the resulting file. * * _easy to configure_ You should be able to configure & customize it to suit your needs. As such, css, javascript and templates are all configurable. |
PackageName | perl-TAP-Formatter-HTML |
PackageRelease | lp153.3.1 |
PackageVersion | 0.11 |
SHA-1 | 9F3394E33CEFD011E38A44C9D9264991A6064D39 |
SHA-256 | 056AC0BCB42FC6FFF15715256B29C986B87891D4EB4DB16551EEDF113E9A5E88 |
Key | Value |
---|---|
MD5 | 609A9F105184683B355BCC19EAAF773C |
PackageArch | noarch |
PackageDescription | This module provides HTML output formatting for the TAP::Harness manpage (a replacement for the Test::Harness manpage. It is largely based on ideas from the TAP::Test::HTMLMatrix manpage (which was built on the Test::Harness manpage and thus had a few limitations - hence this module). For sample output, see: the http://www.spurkis.org/TAP-Formatter-HTML/test-output.html manpage This module is targeted at all users of automated test suites. It's meant to make reading test results easier, giving you a visual summary of your test suite and letting you drill down into individual failures (which will hopefully make testing more likely to happen at your organization ;-). The design goals are: * * _easy to use_ Once you've got your test report, it should be obvious how to use it. * * _helpful_ It should be helpful by pointing out _where_ & _why_ your test suite is breaking. If you've written your tests well, it should give you enough info to start tracking down the issue. * * _easy to install_ Eg: should be a clean install from CPAN, and you shouldn't need to modify your existing test suite to get up & running, though _you will need to stop using the Test::Harness manpage unfortunately_. * * _work out of the box_ You shouldn't need to do any custom-coding to get it working - the default configuration & templates should be enough to get started with. Once installed it should be a matter of running: % prove -m -Q --formatter=TAP::Formatter::HTML >output.html From your project's home dir, and opening the resulting file. * * _easy to configure_ You should be able to configure & customize it to suit your needs. As such, css, javascript and templates are all configurable. |
PackageName | perl-TAP-Formatter-HTML |
PackageRelease | lp152.1.1 |
PackageVersion | 0.11 |
SHA-1 | 4C8DC2A344786A6D0802BA06269E948B6CFBC54E |
SHA-256 | CD5A51AC8A8D23054B569E74F089A03F58BF1239FD09B9661B7896453E1BE8D4 |