Sheila Mooney wrote:
I have been dogfooding Chandler for a while. Looking at the complete
list of performance scenarios...
http://wiki.osafoundation.org/bin/view/Journal/CalendarDogfoodPerformanceScenarios
The top 5 items that I find the most bothersome are...
+ Switching between calendars
+ Activating/Deactivation calendars using checkboxes
+ Double clicking to create a new event
+ Stamping events as a communication
+ Changing the view - going week to week or clicking on mini cal to go
to a particular week
It would be great to have 5 - 10 tests to really focus on in the near
term. Given this list (also echoed by Ted), the beginnings of a proposal...
Highlight these tests we have already:
- New event from double clicking
- Overlay calendar (same as activate/deactivate using checkboxes)
- Jump calendar by one week
- Stamp (perhaps adjusted to be stamp as communication)
And a new test we can easily write:
- Switching between calendars
We probably also need a sharing/syncing test.
I'd like to see us run these tests against the 3k calendar (for
comparison to previous releases), our new sample data set that the QA
team is working on, and some even larger data set (~10k). We should set
targets for the sample data set.
I think we should alter the tinderbox reporting to highlight the 6 tests
above against the target data set, so list them first.
I think we should also write some dashboard/table tests, perhaps
starting with:
+ Scroll table
+ New item from menu in dashboard
+ Switch to dashboard view (from calendar view)
Other dashboard scenarios aren't really implemented yet.
http://lists.osafoundation.org/pipermail/design/2006-May/004722.html
Cheers,
Katie
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
