[cosmo-dev] Cosmo .10 testing status

[Adam Christian]

My steps for an RC have always been the following:
	1. Run the automated tests on all of the supported browsers on all  
the supported browsers
	2. Dump each of these tests runs perf numbers to a text file, and  
compare to make sure nothing looks out of line
	3. Then I do various manual scenarios to ensure that ajaxy  
functionality is behaving the same on each of the browsers:
		This includes the dialogs, collapsable sections in the detail view,  
expansion of recursion, all day even area, now the quick create and  
mini cal, etc.
	4. I manually test multiple sharing scenarios to ensure we don't have  
any regressions here (Still hard to automate)
	5. Once this all checks out, I bring up the bug list are validate any  
bugs that directly touch the UI.
	6. Usually request a qa session to get a larger cross section of  
people using the app at the same time.

As for .10 I am currently on step 4.

Adam

On Nov 28, 2007, at 11:19 AM, Jared Rhine wrote:

> Adam wrote:
>>>> I am still in the process of automated testing...
>
> Jared wrote:
>>> Sorry, could you repeat the specific automation list?
>
>> My piece of this is the automated tests, bug validation, and manual  
>> walk through of a small set of things on multiple platforms.
>
> Ok, thanks.  Most of confusion was you said you were doing  
> "automated tests" when your automated test pieces were already  
> complete.
>
> There weren't any 0.10 bugs marked validated; are there ones you did  
> officially?
>
> Earlier in the 0.10 release process, I suggested to this list a  
> specific list of bugs that seemed especially appropriate for a  
> manual walk through?  Since you did a small manual walk through,  
> were any of those bugs included in your list?
>
> -- Jared
>
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev