[Cosmo-dev] QA Test Scripts

[Adam Christian]

Probably the best thing for manual testing is to get a checklist  
going on a wiki page so people can add those details.

Mikeal, Aparna?

Adam

On Jan 30, 2007, at 3:48 PM, Bobby Rullo wrote:

> What about non-automatable stuff?
>
> Like "verify feature x doesn't look wack when doing ___"
>
> Bobby
>
>
> On Jan 30, 2007, at 3:37 PM, Adam Christian wrote:
>
>> Since I am writing the initial Cosmo QA Test scripts in our new  
>> framework this week.. probably all of the methods you stated will  
>> find their way to my lap so I can incorporate the functionality.  
>> After the first round of them is written they will be committed to  
>> the Cosmo repo so you can go add/edit them etc. I will send out an  
>> email with some direction as soon as that is ready. The hope is to  
>> have a large chunk of the UI automation done and ready for  
>> everyone to use by 0.6.1.
>>
>> Adam
>>
>>
>> On Jan 30, 2007, at 3:29 PM, Bobby Rullo wrote:
>>
>>> Aparna, Adam, Mikeal et al,
>>>
>>> I found a bug before that was so glaring that I was convinced it  
>>> must've not been in the test scripts. I have since realized that  
>>> it's due to a weird interaction of things in my local environment  
>>> so I never bugged you guys about it.
>>>
>>> But the general question remains, what is the best way to ensure  
>>> that certain scenarios, features, make it into the QA Test  
>>> scripts? Are the scripts publicly available somewhere? Can I edit  
>>> them or at least add a comment? Or should file a bug? Or ________?
>>>
>>>
>>> Thanks,
>>>
>>> Bobby
>>> _______________________________________________
>>> cosmo-dev mailing list
>>> cosmo-dev at lists.osafoundation.org
>>> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev
>>
>