[cosmo-dev] Cosmo .10 testing status

[Mike Taylor]

On Nov 27, 2007, at 2:44 PM, Jared Rhine wrote:

>> I am still in the process of automated testing...
>
> Sorry, could you repeat the specific automation list?
>
> (Full list is, I believe: Unit, Windmill, Protocol, Migration)
>
> Is the status:
>
> Unit: Done by tinderbox
> Windmill: Done before RC
> Protocol: Being done now
> Migration: 0.10 includes a schema change, so being done now.
>
> There seems to be an emerging consensus that with our new capability  
> to do "one-button build" test instances, we can (and should) move  
> from:
>
>  (old): "cook RC, put on qacosmo, then kickoff formal testing"
>
> to
>
>  (new): "push 'next release button', confirm automated testing and  
> sanity test of new features against that tree, then cook RC".
>
> We did the Windmill validation before the RC this time, a nifty  
> innovation.  I propose that we continue to do that; it just makes  
> sense (of course, it will be done automatically by Tinderbox by at  
> least a subset of supported browsers).

I think adam uses a version of Windmill that is custom or hasn't been  
pushed as a release - the tinderboxes are running now for two browsers  
and showing test failures.  I upgrade them when I get notified of new  
windmill versions and right now that is when I see the announcement  
either on the windmill list or via cheeseshop.

--
bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
bear at osafoundation.org
http://www.osafoundation.org

bear at code-bear.com
http://code-bear.com