[Cosmo-dev] Cosmo UI Performance Testing Cont.

[Ted Leung]

+1 to all these questions.  Specifics for a lot of the below would  
help -- which pages, which data set, etc.

Ted

On Dec 14, 2006, at 3:16 PM, Jared Rhine wrote:

> On Thu, 2006-12-14 at 14:26 -0800, Adam Christian wrote:
>> 	-Testing page load times
>
> Are there particular pages you've got in mind?  I think login page  
> load
> and the calendar UI page loads are the ones that need to be included.
> You mention "calendar UI load times" as your second point, so maybe
> there's some overlap between the 3 items you propose.
>
> To test caching, test calendar UI "reload" would be great, if you can
> trigger that via the test framework.
>
>> 	-Testing specific tests and test suites running times
>
> Sounds pretty general.  Is there "specific tests and test suites"
> already written that will be timed?
>
>> 	- Adding/Removing/Updating event
>> 	- Setting up various recurring events
>> 	- Switching between Calendars
>
> These are good candidates, yeah.
>
> Seems like some of the non-UIish stuff could in theory be testing
> through the browser, like webcal get maybe.
>
> Some dashboard stuff could/should be included.  Perhaps change of the
> triage status on 3 items then hitting the triage button.
>
> What calendar data sets are going to be used?
>
> -- 
> Jared Rhine <jared at wordzoo.com>
>
>
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev