Key | Value |
---|---|
FileName | ./usr/share/man/man3/TAP::Formatter::HTML.3pm.gz |
FileSize | 6780 |
MD5 | AB012262022BBDECC31DC2C8B5C7FE27 |
SHA-1 | 4E929E92877648B7F4D62168B9A127EBA60E59E3 |
SHA-256 | E7DA0A2943B5FA1AFCCF3F6E0F3DE5E4494159D7CEA762EC1055024850C37C2A |
SSDEEP | 192:3I+O2ontAmnXD4A9tXhTbJ4ZrAz7g6xpnD:3It/ymnXHtlJ4ZrAz7g6xpnD |
TLSH | T17EE19F4FEEA0E8236FB160845FFFB629F264AA42DD20E97014B365C07349515E20C8A8 |
hashlookup:parent-total | 4 |
hashlookup:trust | 70 |
The searched file hash is included in 4 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 84DA3F244E2DB5AC00B4D3101760F9A7 |
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 | 3.45 |
PackageVersion | 0.11 |
SHA-1 | 20888E073F903270D5D53E8B5191C7C4A33EEB58 |
SHA-256 | 50E4E8A6903029ACCA0F0247EA7AFEBB1748767526F7C617670BAD7842B2E6DE |
Key | Value |
---|---|
MD5 | 3045358B126B0DB224B97D53BC3FA076 |
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 | 3.33 |
PackageVersion | 0.11 |
SHA-1 | 9199D4A3553A4CF54BDDA670F3CCC8885AC0AB93 |
SHA-256 | 617884594F675E0ECC681ECD14208AC2593BC25A8C35A31916812E0ED7D26553 |
Key | Value |
---|---|
MD5 | F5165C170341B88AB1A97B754AAC56F3 |
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.64 |
PackageVersion | 0.11 |
SHA-1 | 5FF1D6E4AE43CE7AC11ADCEB29CFF123BAFAA367 |
SHA-256 | 46C39F9D569E27BBC75864F3DF4A67D0B801CCC597A14CD5DD9DB8F6ED135415 |
Key | Value |
---|---|
MD5 | DE74D34BB5FD2895B329E7D57AD93B82 |
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 | 3.49 |
PackageVersion | 0.11 |
SHA-1 | 4CA798FB39D8C7CEFD199A5FCCD22148E2F1718F |
SHA-256 | EC93F09A23C5F4026B59EF16BFB4421317758F98F27025E4EF4EF28F1649F1B1 |