2012/3/27 Patrick Ohly <[email protected]>: > For example, running a command line operation is not tested. Support for > it is implemented, but only without the output handling. Before adding > that, the tests from the Cmdline unit tests should be incorporated into > test-dbus.py. That way it can be verified that the tests work (because > they fail initially with the new branch) and developing the feature > becomes easier (because testing doesn't have to be manual).
I started working on it yesterday. Just to be sure - do all of the tests from syncevo/Cmdline.cpp have to be ported? Also, I guess that I can pass any value to be under 0th index of args parameter for session.Execute()? I have seen "client-test" to be passed in TestCmdline class, but it seems to be used nowhere in Cmdline anyway. > > -- > Best Regards, Patrick Ohly > > The content of this message is my personal opinion only and although > I am an employee of Intel, the statements I make here in no way > represent Intel's position on the issue, nor am I authorized to speak > on behalf of Intel on this matter. > > _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
