This a place to track issues and enhancement ideas for Chandler tests

Logging

• log output should be configurable separately from console output
• logging should be controlled from a config file rather than so many command line options
• need more informative messages when chandler fails to run at all or quits abruptly during tests

Sharing

• test the subscribe read only, unsubscribe, subscribe read-write scenario described in bug 6504

New tests

• something to test freebusy
• test for reminders
• long running chandler test - be nice to have a chandler install that only infrequently gets update (once a month?) and periodically changes things on the calendar (like bug 6414). Would be nice to have a script that did this but doing it manually would be worthwhile as well.
• Test for search

uncategorized

• need a way to test network resources so that
  • folks are alerted when they go down for a long time (half a day)
  • tests don't report failure when the network resource is the problem
• if a bug is causing a test to fail it would be nice automatically ignore failures until bugzilla reports the bug resolved
• Tests must fail if a traceback occurs this isn't always happening and needs to be resolved
  • make a test that generates an exception that the current logger doesn't catch