[Cosmo-dev] 0.5 status

[Mikeal Rogers]

The "plan" is to automate everything we ever do :) . In terms of  
chandler automation we've recently spent most of our time stabilizing  
the framework so we can get more time to write tests and less time  
fixing issues with the automation system.

TestSharing finds when we seriously break something, minimally I'd  
like to add a FreeBusy test to it. One issue we have is that all the  
functional tests currently have to be run before someone can checkin  
their code, this means that we don't want to automate tests that are  
going to take a long time until we implement some way of  
differentiating between tests the _must_ be run other automated  
tests. This means that the large calendar sharing and updating tests  
that we currently do manually won't be automated in the short term.

I also have a test called cosmo_chandler061 that is a simulation of  
Chandler0.6.1 sharing a single event to cosmo. I plan to add more  
like this in the short term to quickly catch any semantic changes in  
cosmo that may affect Chandler interop.

-Mikeal

On Sep 13, 2006, at 11:17 AM, Ted Leung wrote:

>
> On Sep 13, 2006, at 11:06 AM, Mikeal Rogers wrote:
>
>> Other than that it's all manual, this is one of the things I'll be  
>> running through after you hand me  build though. So other than a  
>> short verification you can let me run through the rest if you have  
>> other things to do.
>
> Is there a plan to automate what is currently manual?
>
> Ted