libtest-www-declare-perl 0.02-1 source package in Ubuntu
Changelog
libtest-www-declare-perl (0.02-1) unstable; urgency=low
[ Rene Mayorga ]
* New upstream release
* raise debhelper and compat level to 7
* debian/control
+ Set Standards-Version to 3.8.0 (no changes needed)
+ refer to module name at long description
+ Move perl from B-D-I to B-D
+ add myself to uploaders
* debian/rules - use dh7 with the help of dh-make-perl -R
* debian/copyright
+ refresh upstream's copyright year
+ Add copyright info about included Module::Install
+ update proposal format
[ gregor herrmann ]
* Make build dependency on libhttp-server-simple-perl versioned.
* debian/control: Changed: Switched Vcs-Browser field to ViewSVN
(source stanza).
-- Ubuntu Archive Auto-Sync <email address hidden> Wed, 29 Apr 2009 12:02:16 +0100
Upload details
- Uploaded by:
- Ubuntu Archive Auto-Sync
- Uploaded to:
- Karmic
- Original maintainer:
- Debian Perl Group
- Architectures:
- all
- Section:
- perl
- Urgency:
- Low Urgency
See full publishing history Publishing
| Series | Published | Component | Section |
|---|
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| libtest-www-declare-perl_0.02.orig.tar.gz | 19.7 KiB | 6b905c852742cb42baa89ec0be85eba5ace4b11c9fca3ffd07615a3c17fa222e |
| libtest-www-declare-perl_0.02-1.diff.gz | 2.0 KiB | 7d022aa43491da2dfb82407237610f291a050db5f477e6810e6c9304a37dce52 |
| libtest-www-declare-perl_0.02-1.dsc | 1.5 KiB | cf2fc1e7fa911053583aee4ef5fc2304dc0ba4810d332ef620db7d6b220fdf51 |
Available diffs
- diff from 0.01-1 to 0.02-1 (15.4 KiB)
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.
