Re: [SyncEvolution] writing unit tests for our new D-Bus API

2009-10-14 Thread Patrick Ohly
On Tue, 2009-10-13 at 15:38 +0100, Patrick Ohly wrote: dbus-monitor buffers its output and doesn't flush it when exiting, which means that output is lost. Stupid dbus-monitor. No solution :-/ dbus-monitor has broken SIGINT handling and no handling of SIGTERM. Because of its brokeness, distros

Re: [SyncEvolution] writing unit tests for our new D-Bus API

2009-10-14 Thread Patrick Ohly
On Tue, 2009-10-13 at 15:38 +0100, Patrick Ohly wrote: What do you think about this? As there were no cries of outrage, I went ahead and improved the test script. While extending the tests I already found different issues in the implementation: * Server.GetConfigs() missing *

[SyncEvolution] writing unit tests for our new D-Bus API

2009-10-13 Thread Patrick Ohly
Hello! We are getting to a point where the D-Bus API should be usable for the GUI. The new code still needs to be tested, which is only possible by adapting the sync-UI and/or writing Python scripts to call the API. This is not a satisfactory situation. We should have the possibility to run such