libtest-www-declare-perl 0.02-7 source package in Ubuntu
Changelog
libtest-www-declare-perl (0.02-7) unstable; urgency=medium * Add explicit runtime dependency on libhttp-server-simple-perl. Thanks to ci.debian.net. * Update years of packaging copyright. * Declare compliance with Debian Policy 4.6.2. * Set Rules-Requires-Root: no. * Update alternative test dependencies. * Annotate test-only build dependencies with <!nocheck>. * Update lintian override (formatting). -- gregor herrmann <email address hidden> Wed, 28 Dec 2022 20:23:57 +0100
Upload details
- Uploaded by:
- Debian Perl Group
- Uploaded to:
- Sid
- Original maintainer:
- Debian Perl Group
- Architectures:
- all
- Section:
- perl
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section | |
---|---|---|---|---|
Oracular | release | universe | perl | |
Noble | release | universe | perl | |
Mantic | release | universe | perl | |
Lunar | release | universe | perl |
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
libtest-www-declare-perl_0.02-7.dsc | 2.5 KiB | fedca03eb4fd3050802f65034f0bc8ee5af36baf5a3a2327cc75f6617be2e3bc |
libtest-www-declare-perl_0.02.orig.tar.gz | 19.7 KiB | 6b905c852742cb42baa89ec0be85eba5ace4b11c9fca3ffd07615a3c17fa222e |
libtest-www-declare-perl_0.02-7.debian.tar.xz | 4.3 KiB | 9e1bfe1bd630d5a6deaa858c4712136910d93f1b9a2360bd7f4951bc92b7afb2 |
Available diffs
- diff from 0.02-6 to 0.02-7 (1.2 KiB)
No changes file available.
Binary packages built by this source
- libtest-www-declare-perl: declarative testing module for web apps
Often in web apps, tests are very dependent on the state set up by previous
tests. If one test fails (e.g. "follow the link to the admin page") then it's
likely there will be many more failures. Test::WWW::Declare aims to alleviate
this problem, as well as provide a nicer interface to Test::WWW::Mechanize.
.
The central idea is that of "flow". Each flow is a sequence of commands ("fill
in this form") and assertions ("content should contain 'testuser'"). If any of
these commands or assertions fail then the flow is aborted. Only that one
failure is reported to the test harness and user. Flows may also contain other
flows. If an inner flow fails, then the outer flow fails as well.