On Fri, 2009-11-27 at 06:17 +0000, Zhu, Yongsheng wrote: > I write some test cases design for GetStatus/StatusChanged signals and > GetProgress/ProgressChanged signals. > Please see the attachment.
Looks reasonable. I was wondering whether those tests which run a full sync should be combined. Advantage: shorter overall runtime. Disadvantage: the different aspects cannot be tested independently. Your choice (that way I don't have to decide ;-) > But it seems that it is hard to do checkings for > GetProgress/ProgressChanged accurately. That's true. Basic sanity checking as you suggested (increasing progress, etc.) looks reasonable. Regarding test-dbus.py in general: some method of controlling the currently hard-coded global settings would be useful, together with documenting them. I didn't do that initially because it wasn't sure how useful the script and individual options are, but it seems to be useful, so let's make it not just useful, but also nice. One option that I keep changing in the source often is debugger = "gdb" to enable an interactive debug session of the syncevo-dbus-server during a test. The other option that at least needs to mentioned is the dependency on a valid HTTP server configuration, currently hard-coded at "scheduleworld_1". -- Best Regards Patrick Ohly Senior Software Engineer Intel GmbH Open Source Technology Center Hermuelheimer Strasse 8a Phone: +49-2232-2090-30 50321 Bruehl Fax: +49-2232-2090-29 Germany _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
