| 1 |
Source: libtest-www-mechanize-perl |
| 2 |
Maintainer: Debian Perl Group <[email protected]> |
| 3 |
Uploaders: gregor herrmann <[email protected]>, |
| 4 |
Damyan Ivanov <[email protected]>, |
| 5 |
Ansgar Burchardt <[email protected]>, |
| 6 |
Peter Pentchev <[email protected]> |
| 7 |
Section: perl |
| 8 |
Testsuite: autopkgtest-pkg-perl |
| 9 |
Priority: optional |
| 10 |
Build-Depends: debhelper-compat (= 13) |
| 11 |
Build-Depends-Indep: libcarp-assert-more-perl <!nocheck>, |
| 12 |
libcgi-pm-perl <!nocheck>, |
| 13 |
libhtml-form-perl <!nocheck>, |
| 14 |
libhtml-lint-perl <!nocheck>, |
| 15 |
libhtml-parser-perl <!nocheck>, |
| 16 |
libhttp-message-perl (>= 6.29) <!nocheck>, |
| 17 |
libhttp-server-simple-perl <!nocheck>, |
| 18 |
libtest-longstring-perl <!nocheck>, |
| 19 |
libtest-pod-coverage-perl <!nocheck>, |
| 20 |
libtest-pod-perl <!nocheck>, |
| 21 |
liburi-perl <!nocheck>, |
| 22 |
libwww-mechanize-perl <!nocheck>, |
| 23 |
libwww-perl <!nocheck>, |
| 24 |
netbase <!nocheck>, |
| 25 |
perl |
| 26 |
Standards-Version: 4.6.1 |
| 27 |
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libtest-www-mechanize-perl |
| 28 |
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libtest-www-mechanize-perl.git |
| 29 |
Homepage: https://metacpan.org/release/Test-WWW-Mechanize |
| 30 |
Rules-Requires-Root: no |
| 31 |
|
| 32 |
Package: libtest-www-mechanize-perl |
| 33 |
Architecture: all |
| 34 |
Depends: ${misc:Depends}, |
| 35 |
${perl:Depends}, |
| 36 |
libcarp-assert-more-perl, |
| 37 |
libhtml-form-perl, |
| 38 |
libhtml-parser-perl, |
| 39 |
libhttp-message-perl (>= 6.29), |
| 40 |
libtest-longstring-perl, |
| 41 |
libwww-mechanize-perl, |
| 42 |
libwww-perl |
| 43 |
Recommends: libhtml-lint-perl |
| 44 |
Description: module for testing web applications |
| 45 |
Test::WWW::Mechanize is a Perl module framework for testing web applications. |
| 46 |
It extends the functionality of WWW::Mechanize (see libwww-mechanize-perl) by |
| 47 |
subclassing it, providing additional features for testing web applications. |
| 48 |
In particular, it provides much nicer diagnostics upon failure. |