[Chandler-dev] Improving the Functional Test Framework

[Aparna Kadakia]

Hello all,
As we are closing in on our alpha4 release, we plan to use the next  
few weeks on improving the Functional Test framework. We plan to meet  
tomorrow at 3 pm to discuss what concrete steps we need to take in  
that direction for both development and QA.

If you have any ideas or input feel free to attend. We will have the  
bridge for the remote people to dial in.

Mikeal will reserve a conference room and let everyone know.

Thanks
Aparna

Begin forwarded message:

> From: Philippe Bossut <pbossut at osafoundation.org>
> Date: November 17, 2006 4:10:23 PM PST
> To: John Anderson <john at osafoundation.org>, Mikeal Rogers  
> <mikeal at osafoundation.org>
> Cc: Aparna Kadakia <aparna at osafoundation.org>, Dan Steinicke  
> <dan at osafoundation.org>
> Subject: Re: Functional scripts work
> Reply-To: pbossut at osafoundation.org
>
> Hi,
>
> We should set up a meeting to discuss this since there's some  
> confusion here on what is our (Apps team) objective in having John  
> spending some time with QA on improving the Functional Tests  
> framework.
>
> Would Tuesday 3pm work for you guys? (we won't have a Design  
> session Tuesday).
>
> Cheers,
> - Philippe
>
> John Anderson wrote:
>> Hi Mikeal:
>>
>> I'd like to meet with you guys to discuss some ideas about what to  
>> work on. My current ideas include:
>>
>> - Add code that catches error before they propagate too far  from  
>> the source of the problem
>>
>> - Simplify the code by reducing layers and replacing some chandler  
>> specific apis with more general apis to reduce the work that has  
>> to be done on the library as Chandler evolves
>>
>> - Spend a day or two investigating recording of scripts
>>
>> - Work with you guys to transfer my Chandler knowledge so you'll  
>> also be able to improve the code.
>>
>> John
>>
>> On Nov 17, 2006, at 12:51 PM, Mikeal Rogers wrote:
>>
>>> Philippe has mentioned that John plans on doing a few weeks worth  
>>> of work rewriting a lot of the CPIA layer.
>>>
>>> Since we are planning a rewrite of ChandlerTestLib it seems  
>>> appropriate that we keep an eye on any API changes and do our  
>>> work in ChandlerTestLib right after the CPIA work is done.
>>>
>>> I was wondering what changes you were planning to make and when,  
>>> and if this is going to be done in a branch (seeing as it will  
>>> most likely break all of the tests).
>>>
>>> -Mikeal
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20061120/11ca490e/attachment.htm