[Catalyst] semi-OT: is it possible to circumvent tests that are related to WWW::Mechanize?

[Joe Landman]

Hi folks:

   Working on deploying a Catalyst app on a customers machine. 
Installation is going well ... until the Catalyst modules that depend 
upon WWW::Mechanize and family come up.

   As far as we can tell, the breakage is not the modules, but the 
WWW::Mechanize (and therefore, by extension, things that use 
WWW::Mechanize).

   Is it possible to simply disable the use of this module during 
installation and testing?  This is on an internal customer-site machine, 
with no easy access to the rest of the net, and WWW::Mechanize really 
wants access to the rest of the net (with a whole lotta hardcoded tests 
to wikipedia and other such things).

   I could "force" it, but so many things seem to depend upon it for 
testing ...

   Advice, clues, pointers are welcome.

-- 
Joe Landman
landman at scalableinformatics.com