From: Eric Hodel <drbrain@...7.net>
Date: 2007-10-15T09:27:28+09:00
Subject: Re: Testing - Network Layer Fault Injection in Ruby

On Oct 14, 2007, at 14:52 , James Tucker wrote:
> Thanks, that's somewhat the route I had started down for some of  
> the units. I probably shouldn't have omitted from my orignal  
> question, the fact that I'm also using OpenSSL.
>
> Some of the specific issues I have been dealing with are caused by  
> a harsh environment (trans-atlantic links and poor ADSL  
> connections), and in some cases this causes irrecoverable blocking.  
> I think I've managed to cover all of the blocking cases, but local  
> tests are hard to implement, as you have to fake things like a full  
> TCP connection timeout. (Which requires not sending and timing out  
> packet data which normally the OS doesn't want you to do).
>
> It's also difficult to find out where the blocks are, as the state  
> renders the app essentially useless, and happens in a different  
> environment than that of the testing / development stage.
>
> As some of this connection state stuff is actually outside of pure  
> ruby, I was somewhat hoping for an external solution, such as a  
> fault injection proxy socket or similar. Do you know of any?

I don't I've not needed that level of fault tolerance.

--
Poor workers blame their tools. Good workers build better tools. The
best workers get their tools to do the work for them. -- Syndicate Wars