http://bugs.meego.com/show_bug.cgi?id=5609
--- Comment #5 from pohly <[email protected]> 2010-09-09 02:37:04 PDT --- (In reply to comment #4) > Dbus-testing has been merged into nightly. The source code has been in > syncevolution/test now. That much I see in the "dbus-testing" branch. There's now a new test/getResult_send.py script. Please, pick a better name. It is not at all obvious from the name which results are meant, and the comment at the top of the file adds no additional information either ("get the results and send them"). Such comments are totally redundant. But where is the documentation on how to integrate this script with the "runtest.py" invocation? What assumptions are made about the work environment? How does it relate to test-dbus.py? For example, showTestCases() opens a testCaseNames.txt in the work path. Does that mean that defining the work path is mandatory? Where does that file come from? There are some example invocations, but they seem to be incomplete. > Configurations are separated from testing by adding some command line options. > > 'Dbus-testing' will use the same syncevolution source code with > 'syncevolution-testing', but compile its own binary using different compile > flags against 'syncevolution-testing'. 'Dbus-testing' will be skipped if the > binary was not compiled successfully. Sorry, I don't understand how this is meant to work. What I expect to happen is this: - runtest.py is used to compile binaries - if the binaries were compiled successfully, also run test-dbus.py using them and send out the results -- Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
