Katie Capps Parlante wrote: > 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 have tests that measure publishing and subscribing speed, but these are not yet enabled by default (I was a little concerned about the sharing functional test being disabled, but it seems Windows only and even then it might only be a problem in the functional tests that does not restart Chandler for each test). Is mail syncing also something you use and which is slowing you down? > 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. The problem is that running the performance tests takes quite a bit of time so there is a limit on how many new tests we can reasonably add. And removing existing tests means we'll lose the ability to compare to past. I think we could remove some tests, though. > I think we should also write some dashboard/table tests, perhaps > starting with: > + Scroll table I think we have this test already. > + Switch to dashboard view (from calendar view) I think we also have this test. -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
