As it's of relevance to QA (by way of testing), I wanted to let folks
know that I have recently put LWP::UserAgent::Mockable onto CPAN.
This allows easy mocking of LWP by permitting LWP sessions to be
recorded to file, and later played back. Normal behaviour (no
modifying of requests/responses) is
Would a lock on STDOUT not achieve the same effect, 1/ without having
to introduce new syntax and 2/ while appearing more responsive to the
user?
You'd also still potentially get output conflated, as atomic write
size is a fixed size (I believe in the order of 2-4K on most systems,
looks to be 2K
On Tue, Jul 7, 2009 at 3:15 AM, Michael G Schwern wrote:
> use lib 't/lib';
> chdir 't';
> require Some::Module::In::t::lib;
>
> lib.pm does not make the directory absolute, so it leaves your program
> vulnerable to the above problem. Its rare you'd have to require instead of
> use, some load orde
On Tue, Jul 7, 2009 at 9:21 PM, Michael G Schwern wrote:
> Mark Morgan wrote:
>> [1] Test::Class is my preferred testing package for work; I don't use
>> it for stuff destined for CPAN due to adding an extra dependancy.
>> *sigh*
>
> Your CPAN modules already depe
On Mon, Aug 24, 2009 at 6:37 PM, Jonathan Swartz wrote:
> Yes, getting the pid from each process launch is not the problem - it's
> more of a wish that I could do this automagically somehow, instead of
> having to collect all the pids somewhere. But it seems as if I'll have
> to do that.
Is it fea
(apologies if you get 2 versions of this; My phone crashed as I was
composing a reply on train... :( )
Heya Sprios,
I'l give a shameless plug for LWP::UserAgent::Mockable. This was originally
written for testing complex web services (and to get around the situation of
same being quite unreliable
