http://bugs.meego.com/show_bug.cgi?id=5609
--- Comment #26 from pohly <[email protected]> 2011-01-24 23:22:07 PST --- (In reply to comment #25) > (In reply to comment #24) > > This could be done with the "setup-evolution" script in the nightly test > > setup. > > Is this script in syncevolution-testing : "setup-syncevolution.sh"? Yes. > I have some questions about this script. > Does this script change with SyncEvolution update? How is this script created? This script is maintained manually and typically does not change. It contains the credentials and per server/host configuration options. Because of that confidential information it cannot be in the public SyncEvolution repo. > This script is used to setup client-test configuration and is not about > dbus_unittest configuration. How can we use this script to get configuration > for dbus-testing? Patrick, Could you provide some detail about creating > configuration each time dbus-testing starts? You could add "dbus_testing" as an alternative name for some existing server: memotoo*|dbus_testing) ... Then further down, in addition to creating two configs for client-test (for client in 1 2; do ...), also create the $TEST config for the D-Bus tests. To use this modified script, invoke it before running test-dbus.py. -- 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
