[Cosmo-dev] Areas that could use some testing...

[Aparna Kadakia]

Hello All,
Given that we are in the last stage of getting to ZBR (Zero Bug  
Release) on both the projects, we are now getting into the critical  
phase of stabilizing the product over the next few weeks for Preview.

Lately we have seen some rather obscure bugs in different areas of  
that app, that are not only hard to reproduce but also quite  
transient. We have seen them happen off and on and some of them  
isolated to shared collections. Another observation has been that  
working on a shared collection updated by mutiple people over a  
period of time has led to some weird ad-hoc failures . We haven't  
been able to nail the failures down to any set of repro steps yet but  
here are some bugs filed for those and we could use help in getting  
reproduction steps for these failures.

bug 10435    	Index error on repo (repairable) :
     https://bugzilla.osafoundation.org/show_bug.cgi?id=10435
bug 10402    	Adhoc and other index errors
    https://bugzilla.osafoundation.org/show_bug.cgi?id=10402
bug 10401	Traceback when starting chandler
    https://bugzilla.osafoundation.org/show_bug.cgi?id=10401
bug 10391   	"NoSuchAttributeError" for  
"CalendarSelection.selectedOcc...
    https://bugzilla.osafoundation.org/show_bug.cgi?id=10391
bug 10349  	Cannot select-all in Dashboard
    https://bugzilla.osafoundation.org/show_bug.cgi?id=10349

So over the next week or so, if you have any free cycles we could use  
some help in :
1. getting the repro steps for the above bugs and
2. testing the following work flows that have produced random, ad-hoc  
failures at times

1. Updating items in shared collections by multiple people . Add to  
this, updating the same item by a different user from Cosmo web UI  
and validating the change to item and byline in Chandler.
2. Creating recurring events in shared collections and copying them  
to other shared collections. Creating multiple exceptions in the  
series with all the recurrence change options.
3. Stamping recurring events as mail and sending invites to more than  
1 person. Updating these sent/received items by senders and receivers.
4. Updating triage status of recurring events in shared collections.
5. Modifying recurring events from the Dashboard (not calendar canvas)
6. Downloading mail and draggging them to different folders and  
having them updated.

I will go ahead and add these to the Integration Test spec as well.  
Let me know if you have any questions.

Thanks and have a good weekend,
Aparna