Since writing my initial post on my settings for the Perl debugger I’ve found another setting that I’ve found to be invaluable. If you create a file, ~/.perldb it will load your settings each time, mine now has two lines on whatever machine I’m using,
$DB::deep = 1000;
dumpDepth=2 trick is something I picked up from Chisel’s blog post on the subject and simply limits your x to a depth of 2 by default. This makes life a lot simpler and means I get caught out by accidentally dumping the entire state of an application less often.
Or should that be getting real? The Test::WWW::Mechanize::Catalyst module has a really handy feature, with the
CATALYST_SERVER environment variable you can set to point your tests at a real live server. This is really handy for a couple of things. One of those being monitoring real traffic for those cases where you can’t quite decide whether it’s your test or your server that’s broken. You can fire up Wireshark and watch the actual traffic going over the wire.
With Test:::WWW:Mechanize::PSGI there doesn’t appear to be that option, and Test::WWW::Mechanize and the modules it wrap don’t really appear to have any simple way to provide that. A look at the T:W:M:Catalyst module suggests it’s actually a nice chunk of work that they did to implement that feature. Since I’m lazy and I wanted to solve a problem I came up with a simple way to fake it for now. I converted the urls from simple
/path to proper qualified
http://localhost:5000/path urls in my tests then added a simple bit of code to flip between
$mech = Test::WWW::Mechanize->new;
my $app = Plack::Util::load_psgi 'app.psgi';
$mech = Test::WWW::Mechanize::PSGI->new( app => $app );
Now if I run the tests with
EXTERNAL_SERVER=1 it goes to a real server rather than straight to code. That means I can listen on the loopback adaptor in Wireshark and see what’s actually going over the wire simply. It’s not as neat as the
CATALYST_SERVER feature, but it does for now.