[Chandler-dev] Proposal to deal with network errors in tests

[Andi Vajda]

On Wed, 13 Sep 2006, Heikki Toivonen wrote:

> Andi Vajda wrote:
>> +1 as long as you provide yet another command line flag to disable all
>> such tests that access the network. This is important when no network is
>> available or really slow. For example, running the flickr tests over
>> dialup takes about 10 minutes.
>
> I think that is orthogonal to my proposal. We don't currently have such
> a flag either, but we have a bug to run Chandler in offline mode.
> However, we also have unit tests and you can't really provide a command
> line flag then (there could be an environment variable or something).

it's not that orthogonal since you're proposing to make these tests even 
slower when there are network failures.

As for the unit tests, you're right, it's a little messier there. An env var 
(yuck) could fix it or maybe adding config file-based configuration to our 
unit tests. This would enable disabling some suites without messing with the 
code, enable some to run with a ramdb, others not, some not when there is no 
network, etc... More work for sure. The functional test command line flag 
would be a good start because it would also let chandler run offline without 
breaking.

Andi..