Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
Changes from previous:
0.56 Thu Oct 13 21:05 BRT 2011
- Add port to Host header
0.55 Tue Sep 27 19:20 BST 2011
- Set 'Host' header for remote requests too
0.54 Mon Aug 1 20:49 BST 2011
- change to make sure we support changes in Catalyst::Test introduced
in the Cataplack port.
0.53 Sun Dec 5 23:03 GMT 2010
- Fix tests to work with the upcoming psgi based Catalyst release
as $c->req->header('Host') now more accurately reflects what you
see in a real web server (i.e. the port will not be defined if it
is 80)
- Fix tests to work when the CATALYST_DEBUG environment variable is
set by explicitly setting it to 0 in tests which require it.
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.
sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
pkgsrc changes:
- Adjust license definition
- Adjust dependencies
Upstream changes:
0.52 Mon Mar 8 01:25 GMT 2010
- Move actions out of the test applications to avoid deprecation warnings.
- POD corrections by jhannah
- Bump version dependency of Test::WWW::Mechanize to 1.54 to fix RT#44555
- Wrap checks for the appropriate plugins to skip tests inside a BEGIN
block so that they are run before the app tries to be loaded at compile
time, fixing RT#47037
- Updating package for p5 module of Test::WWW::Mechanize for Catalyst from
0.42 to 0.51
- Setting license to gnu-gpl-v2 # OR artistic
- Adjusting dependencies according to META.yml
Upstream changes:
0.51 Mon Mar 16 10:00 GMT 2009
- Doc updates from thejester
- User agent fixes from ANDREMAR
- Fix bug where redirect was followed on a 500 response
- All remote requests (i.e. CATALYST_SERVER env var) now use our own
mechanize object, rather than an unconfigurable one from Catalyst:Test
0.50 Tue Feb 17 09:12 GMT 2009
- Remove warning in HTTP::Cookies
- Call BUILDALL
0.50_2 Thur Feb 12 09:47 GMT 2009
- Make t/multi_content_type.t handle case when server cant be started,
which is almost always due to port in use.
0.50_1 Thur Feb 5 09:02 GMT 2009
- App classname no longer has to be passed to import:
$m = T::W::M::C->new(catalyst_app => 'Catty')
now works.
- Can now use TWMC two test two different apps in the same perl
interpreter due to the above change
- Removed Test::WWW::Mechanize::Catalyst::Aux package as it isn't needed
any more
- Add 'host' accessor for white-label testing
- Moosification
- Can now test against remote CATALYST_SERVER without having to load the
app class
0.45 Mon Nov 24 20:39:19 GMT 2008
- be forwards-compatible with Catalyst 5.80's virtual
domain testing (thanks Jason Gottshall)
0.44 Mon Oct 27 13:48:22 GMT 2008
- fix longstanding bug with recent LWP, requiring
WWW::Mechanize 1.50 (thanks to petdance, mst, dakkar)
- add machine- and human-readable license, add abstract
0.43 Mon Aug 18 15:42:03 BST 2008
- add missing prereqs to Catalyst::Plugin::Session::State::Cookie
and Catalyst::Plugin::Session::Store::Dummy (thanks kd)
to trigger/signal a rebuild for the transition 5.8.8 -> 5.10.0.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=...").
Catalyst is an elegant MVC Web Application Framework. Test::WWW::Mechanize
is a subclass of WWW::Mechanize that incorporates features for web
application testing. The Test::WWW::Mechanize::Catalyst module
meshes the two to allow easy testing of Catalyst applications
without starting up a web server.
Testing web applications has always been a bit tricky, normally
starting a web server for your application and making real HTTP
requests to it. This module allows you to test Catalyst web
applications but does not start a server or issue HTTP requests.
Instead, it passes the HTTP request object directly to Catalyst.
Thus you do not need to use a real hostname: "http://localhost/"
will do.
