[Chandler-dev] Sane defaults for new Chandler testing framework

[Bryan Stearns]

Just curious: why aren't we using python's logging for tests? We're 
already using it for the rest of the app, and it's got easily 
overridable defaults, levels, alternative streams of output (which could 
be used for the minimal output that tbox needs to detect failures)...

...Bryan

Mikeal Rogers wrote:

> Bear hasn't gotten back to me yet on exactly what he would like for a  
> format on tinderbox.
>
> The default we have for human use shouldn't necessarily be the same  
> as tinderbox. When bear integrated the functional test tool I wrote  
> for cosmo I believe he masked all output and just read the final  
> summary output.
>
> It's trivial to have different output setting on tinderbox and  
> regular human use.
>
> -Mikeal
>
>
> On May 23, 2006, at 4:03 PM, Andi Vajda wrote:
>
>>
>> On Tue, 23 May 2006, Mikeal Rogers wrote:
>>
>>> Hiya,
>>
>>
>>> All of these can be easily set manually, but the question we have  
>>> is "what should the defaults be when running individual tests and  
>>> the functional test suite?".
>>
>>
>> The defaults should be whatever is used by the tinderboxes.
>>
>> Andi..
>>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev