maryjane/syncevolution
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
syncevolution/test/test.am

171 lines
8.9 KiB
Text
Raw Normal View History

Port build system to non-recursive Automake. All but toplevel Makefile.am are replaced with their non-recursive counterparts. The generation of configure.in was removed (and thus configure-{pre,post}.in are also removed) in favor of configure.ac and m4 macros adding backend specific configure parts. Version number is generated like in old build system. There are still many things to improve, but for now there are no immediate regressions. AUTOTOOLS-TODO contains a list of possible improvements and fixes. AUTOTOOLS-TESTING contains what was tested with current build system (configure flags, make options).
2011-08-30 16:24:58 +02:00
dist_noinst_DATA += \
test/abort-redirect.cpp \
test/ClientTest.h \
testing: improved logging + CLIENT_TEST_SOURCE_DELAY Exceptions reported by CppUnit only contained one file+line pair. If that location was called multiple times inside a larger test, then it was impossible to tell where it was called. The new assertion macros and in particular CT_ASSERT_NO_THROW() solve this problem by catching exceptions, adding the current file+line information and then rethrowing an extended exception. When CppUnit finally logs the problem, it will contain a complete call stack. For this to work, every single line which might throw an exception must be wrapped in a macro. Entering and leaving the line is logged together with the wrapped expression as part of the test .log file. doSync() is handled as a special case and gets the file+line info of its caller via parameters. New logging macros are introduced and used in LocalTests::testChanges: instead of writing comments, call the logging macros and the string will appear also in the .log file of the test. Further areas for improvements: - use CLIENT_TEST_LOG() everywhere - reduce file names to just the base name is logged - convert .log file into HTML with links into session logs and ClientTest.cpp source file
2011-11-07 22:02:04 +01:00
test/ClientTestAssert.h \
Port build system to non-recursive Automake. All but toplevel Makefile.am are replaced with their non-recursive counterparts. The generation of configure.in was removed (and thus configure-{pre,post}.in are also removed) in favor of configure.ac and m4 macros adding backend specific configure parts. Version number is generated like in old build system. There are still many things to improve, but for now there are no immediate regressions. AUTOTOOLS-TODO contains a list of possible improvements and fixes. AUTOTOOLS-TESTING contains what was tested with current build system (configure flags, make options).
2011-08-30 16:24:58 +02:00
test/ClientTest.cpp \
test/client-test-main.cpp \
test/test.h \
test/test.cpp
dist_noinst_SCRIPTS += \
test/Algorithm/Diff.pm \
test/syncevo-http-server.py \
test/syncevo-phone-config.py \
test/synccompare.pl \
testing: generate HTML version of .log files and ClientTest.cpp The HTML version of the .log files links to ClientTest.cpp.html, colorizes important parts and links to the sync session directories. Because it is much more useful than the plain text version, the nightly.html now links to these .html files. ClientTest.cpp.html is built with Python pygments if installed, otherwise some builtin fallback code is used.
2011-11-08 12:57:24 +01:00
test/log2html.py \
Port build system to non-recursive Automake. All but toplevel Makefile.am are replaced with their non-recursive counterparts. The generation of configure.in was removed (and thus configure-{pre,post}.in are also removed) in favor of configure.ac and m4 macros adding backend specific configure parts. Version number is generated like in old build system. There are still many things to improve, but for now there are no immediate regressions. AUTOTOOLS-TODO contains a list of possible improvements and fixes. AUTOTOOLS-TESTING contains what was tested with current build system (configure flags, make options).
2011-08-30 16:24:58 +02:00
test/run_src_client_test.sh
testing: simulate remote item manipulation Traditionally, SyncEvolution only modified remote data via syncing. This is not enough because it does not cover data on the remote side that SyncEvolution cannot sync. The new tests solve this by using the command line's import/update operations which modify data more or less directly. Now we can test: - downloading data created remotely - uploading data via sync, export directly, compare - simulate conflicts with changes made remotely The download and upload test include full round-trips, i.e. the initial transfer plus a change that needs to be synced back. Because this is highly dependent on the exact data stored by the peer, all these tests depend on per-peer test data and scripts for modifying that data. The tests only get enabled if the test data is found. The initial test data covers Apple Calendar server, EDS<->EDS and Google Contacts.
2014-04-23 14:53:23 +02:00
test_testcases = \
Port build system to non-recursive Automake. All but toplevel Makefile.am are replaced with their non-recursive counterparts. The generation of configure.in was removed (and thus configure-{pre,post}.in are also removed) in favor of configure.ac and m4 macros adding backend specific configure parts. Version number is generated like in old build system. There are still many things to improve, but for now there are no immediate regressions. AUTOTOOLS-TODO contains a list of possible improvements and fixes. AUTOTOOLS-TESTING contains what was tested with current build system (configure flags, make options).
2011-08-30 16:24:58 +02:00
test/testcases/eds_event.ics \
test/testcases/eds_event.ics.local \
test/testcases/eds_task.ics \
test/testcases/vcal10.ics \
CardDAV: use Apple/Google/CardDAV vCard flavor In principle, CardDAV servers support arbitrary vCard 3.0 data. Extensions can be different and need to be preserved. However, when multiple different clients or the server's Web UI interpret the vCards, they need to agree on the semantic of these vCard extensions. In practice, CardDAV was pushed by Apple and Apple clients are probably the most common clients of CardDAV services. When the Google Contacts Web UI creates or edits a contact, Google CardDAV will send that data using the vCard flavor used by Apple. Therefore it makes sense to exchange contacts with *all* CardDAV servers using that format. This format could be made configurable in SyncEvolution on a case-by-case basis; at the moment, it is hard-coded. During syncing, SyncEvolution takes care to translate between the vCard flavor used internally (based on Evolution) and the CardDAV vCard flavor. This mapping includes: X-AIM/JABBER/... <-> IMPP + X-SERVICE-TYPE Any IMPP property declared as X-SERVICE-TYPE=AIM will get mapped to X-AIM. Same for others. Some IMPP service types have no known X- property extension; they are stored in EDS as IMPP. X- property extensions without a known X-SERVICE-TYPE (for example, GaduGadu and Groupwise) are stored with X-SERVICE-TYPE values chosen by SyncEvolution so that Google CardDAV preserves them (GroupWise with mixed case got translated by Google into Groupwise, so the latter is used). Google always sends an X-ABLabel:Other for IMPP. This is ignored because the service type overrides it. The value itself also gets transformed during the mapping. IMPP uses an URI as value, with a chat protocol (like "aim" or "xmpp") and some protocol specific identifier. For each X- extension the protocol is determined by the property name and the value is the protocol specific identifier without URL encoding. X-SPOUSE/MANAGER/ASSISTANT <-> X-ABRELATEDNAMES + X-ABLabel The mapping is based on the X-ABLabel property attached to the X-ABRELATEDNAMES property. This depends on the English words "Spouse", "Manager", "Assistant" that Google CardDAV and Apple devices seem to use regardless of the configured language. As with IMPP, only the subset of related names which have a corresponding X- property extension get mapped. The rest is stored in EDS using the X-ABRELATEDNAMES property. X-ANNIVERSARY <-> X-ABDATE Same here, with X-ABLabel:Anniversary as the special case which gets mapped. X-ABLabel parameter <-> property CardDAV vCards have labels attached to arbitrary other properties (TEL, ADR, X-ABDATE, X-ABRELATEDNAMES, ...) via vCard group tags: item1.X-ABDATE:2010-01-01 item1.X-ABLabel:Anniversary The advantage is that property values can contain arbitrary characters, including line breaks and double quotation marks, which is not possible in property parameters. Neither EDS nor KDE (judging from the lack of responses on the KDE-PIM mailing list) support custom labels. SyncEvolution could have used grouping as it is done in CardDAV, but grouping is not used much (not at all?) by the UIs working with the vCards in EDS and KDE. It seemed easier to use a new X-ABLabel parameter. Characters which cannot be stored in a parameter get converted (double space to single space, line break to space, etc.) during syncing. In practice, these characters don't appear in X-ABLabel properties anyway because neither Apple nor Google UIs allow entering them for custom labels. The "Other" label is used by Google even in case where it adds no information. For example, all XMPP properties have an associated X-ABLabel=Other although the Web UI does not provide a means to edit or show such a label. Editing the text before the value in the UI changes the X-SERVICE-TYPE parameter value, not the X-ABLabel as for other fields. Therefore the "Other" label is ignored by removing it during syncing. X-EVOLUTION-UI-SLOT (the parameter used in Evolution to determine the order of properties in the UI) gets stored in CardDAV. The only exception is Google CardDAV which got confused when an IMPP property had both X-SERVICE-TYPE and X-EVOLUTION-UI-SLOT parameters set. For Google, X-EVOLUTION-UI-SLOT is only sent on other properties and thus ordering of chat information can get lost when syncing with Google. CardDAV needs to use test data with the new CardDAV vCard flavor. Most CardDAV servers can store EDS vCards and thus Client::Source::*::testImport passed (with minor tweaks in synccompare) when using the default eds_contact.vcf, but Client::Sync::*::testItems fails when comparing synced data with test cases when the synced data uses the native format and the test cases are still the ones from EDS. A libsynthesis with URLENCODE/DECODE() and sharedfield parameter for <property> is needed.
2014-05-16 11:25:00 +02:00
test/testcases/carddav.vcf \
Port build system to non-recursive Automake. All but toplevel Makefile.am are replaced with their non-recursive counterparts. The generation of configure.in was removed (and thus configure-{pre,post}.in are also removed) in favor of configure.ac and m4 macros adding backend specific configure parts. Version number is generated like in old build system. There are still many things to improve, but for now there are no immediate regressions. AUTOTOOLS-TODO contains a list of possible improvements and fixes. AUTOTOOLS-TESTING contains what was tested with current build system (configure flags, make options).
2011-08-30 16:24:58 +02:00
test/testcases/eds_contact.vcf \
test/testcases/eds_memo.ics \
test/testcases/google_event.ics \
test/testcases/yahoo_contact.vcf \
test/testcases/lcs/file1.txt \
test/testcases/lcs/file2.txt \
test/testcases/local.png \
test/testcases/templates/clients/phone/nokia/S40/7210c.ini \
test/testcases/templates/clients/SyncEvolution.ini \
testing: simulate remote item manipulation Traditionally, SyncEvolution only modified remote data via syncing. This is not enough because it does not cover data on the remote side that SyncEvolution cannot sync. The new tests solve this by using the command line's import/update operations which modify data more or less directly. Now we can test: - downloading data created remotely - uploading data via sync, export directly, compare - simulate conflicts with changes made remotely The download and upload test include full round-trips, i.e. the initial transfer plus a change that needs to be synced back. Because this is highly dependent on the exact data stored by the peer, all these tests depend on per-peer test data and scripts for modifying that data. The tests only get enabled if the test data is found. The initial test data covers Apple Calendar server, EDS<->EDS and Google Contacts.
2014-04-23 14:53:23 +02:00
test/testcases/synctests/apple/eds_contact/testUpload/local-synced \
test/testcases/synctests/apple/eds_contact/testUpload/local \
test/testcases/synctests/apple/eds_contact/testUpload/modify-remote \
test/testcases/synctests/apple/eds_contact/testUpload/remote \
test/testcases/synctests/apple/eds_contact/testDownload/modify-local \
test/testcases/synctests/apple/eds_contact/testDownload/local \
test/testcases/synctests/apple/eds_contact/testDownload/remote \
test/testcases/synctests/apple/eds_contact/testDownload/remote-synced \
test/testcases/synctests/googlecontacts/eds_contact/testUpload/local-synced \
test/testcases/synctests/googlecontacts/eds_contact/testUpload/local \
test/testcases/synctests/googlecontacts/eds_contact/testUpload/modify-remote \
test/testcases/synctests/googlecontacts/eds_contact/testUpload/remote \
test/testcases/synctests/googlecontacts/eds_contact/testDownload/modify-local \
test/testcases/synctests/googlecontacts/eds_contact/testDownload/local \
test/testcases/synctests/googlecontacts/eds_contact/testDownload/remote \
test/testcases/synctests/googlecontacts/eds_contact/testDownload/remote-synced \
test/testcases/synctests/googlecontacts/eds_contact/testUpdateRemoteWins/modify-local \
test/testcases/synctests/googlecontacts/eds_contact/testUpdateRemoteWins/local-synced \
test/testcases/synctests/googlecontacts/eds_contact/testUpdateRemoteWins/local \
test/testcases/synctests/googlecontacts/eds_contact/testUpdateRemoteWins/modify-remote \
test/testcases/synctests/googlecontacts/eds_contact/testUpdateRemoteWins/remote-synced \
test/testcases/synctests/googlecontacts/eds_contact/testUpdateLocalWins/modify-local \
test/testcases/synctests/googlecontacts/eds_contact/testUpdateLocalWins/local-synced \
test/testcases/synctests/googlecontacts/eds_contact/testUpdateLocalWins/local \
test/testcases/synctests/googlecontacts/eds_contact/testUpdateLocalWins/modify-remote \
test/testcases/synctests/googlecontacts/eds_contact/testUpdateLocalWins/remote-synced \
$(NOP)
dist_noinst_DATA += \
$(test_testcases) \
test/COPYING \
test/Algorithm/Artistic \
test/Algorithm/COPYING \
test/Algorithm/README \
Port build system to non-recursive Automake. All but toplevel Makefile.am are replaced with their non-recursive counterparts. The generation of configure.in was removed (and thus configure-{pre,post}.in are also removed) in favor of configure.ac and m4 macros adding backend specific configure parts. Version number is generated like in old build system. There are still many things to improve, but for now there are no immediate regressions. AUTOTOOLS-TODO contains a list of possible improvements and fixes. AUTOTOOLS-TESTING contains what was tested with current build system (configure flags, make options).
2011-08-30 16:24:58 +02:00
test/syncevo-http-server-logging.conf \
$(wildcard test/testcases/*.patch)
GDBus: test program for client/server setup Can run as both client and server. Linked against libsyncevolution only because it needs some utility methods in it. Logs authentication state when a new connection is created. Currently such connections are unauthenticated at first. If the client has the same user ID as the server, it is allowed to proceed (tested empirically). If not, authentication fails and handle_message() is not called (but the connection remains open!?). Disconnects are not properly detected because GDBus for libdbus doesn't support reporting disconnects on a connection (not implemented). Instead of relying on it, better watch child or parent via some other means. In this example, the server side just keeps the connection open until the next client connects. The client lets GDBus exit() the process on disconnect.
2011-12-16 08:29:02 +01:00
# generic D-Bus client/server tests
if COND_DBUS
noinst_PROGRAMS += test/dbus-client-server
test_dbus_client_server_SOURCES = test/dbus-client-server.cpp
test_dbus_client_server_CPPFLAGS = -I$(gdbus_dir) -I$(top_srcdir)/src
autotools: use cppcheck.pc Now cppcheck is found via the normal PKG_CHECK_MODULES. The advantage is that CPPUNIT_CFLAGS and CPPUNIT_LIBS can be overridden with configure parameters, which will be used to link cppcheck statically into syncevolution.org binaries (libcppunit ABI has changed).
2016-09-20 16:00:28 +02:00
test_dbus_client_server_CXXFLAGS = $(CPPUNIT_CFLAGS) $(SYNCEVOLUTION_CXXFLAGS) $(BACKEND_CPPFLAGS) $(DBUS_CFLAGS) $(GLIB_CFLAGS) $(GOBJECT_CFLAGS) $(PCRECPP_CFLAGS)
test_dbus_client_server_LDFLAGS = $(CPPUNIT_LIBS)
autotools: allow extending core linker flags These linker flags are added to those normally used for linking against libsyncevolution. The intended usage is to extend linking of syncevolution.org binaries such that static versions of libcppunit, libpcrecpp and libopenobex are used, because the ABI of those libs have changed such that binaries linked on Ubuntu Trusty would not run on more recent distros like Ubuntu Xenial. For example, on Ubuntu Trusty i386 one can configure with: PCRECPP_LIBS=-lpcre \ LIBOPENOBEX_LIBS=-lpcre \ '--with-extra-core-ldadd=/usr/lib/i386-linux-gnu/libpcrecpp.a -lpcre /usr/lib/libopenobex.a /usr/lib/i386-linux-gnu/libusb.a' \ CPPUNIT_LIBS=/usr/lib/i386-linux-gnu/libcppunit.a
2016-09-20 16:06:27 +02:00
test_dbus_client_server_LDADD = $(gdbus_build_dir)/libgdbussyncevo.la src/syncevo/libsyncevolution.la $(DBUS_LIBS) $(GLIB_LIBS) $(GOBJECT_LIBS) $(PCRECPP_LIBS) $(EXTRACORELDADD)
GDBus: test program for client/server setup Can run as both client and server. Linked against libsyncevolution only because it needs some utility methods in it. Logs authentication state when a new connection is created. Currently such connections are unauthenticated at first. If the client has the same user ID as the server, it is allowed to proceed (tested empirically). If not, authentication fails and handle_message() is not called (but the connection remains open!?). Disconnects are not properly detected because GDBus for libdbus doesn't support reporting disconnects on a connection (not implemented). Instead of relying on it, better watch child or parent via some other means. In this example, the server side just keeps the connection open until the next client connects. The client lets GDBus exit() the process on disconnect.
2011-12-16 08:29:02 +01:00
test_dbus_client_server_DEPENDENCIES = $(gdbus_build_dir)/libgdbussyncevo.la src/syncevo/libsyncevolution.la
if ENABLE_UNIT_TESTS
test_dbus_client_server_SOURCES += test/test.cpp
endif
testing: update packaging and testing of pre-compiled binaries Only the "client-test" executable and its test data were installed so far, in /usr/bin resp. the doc dir. Now also test-dbus.py and testpim.py plus their data files get installed, using a new /usr/lib/syncevolution/test directory for all test files and commands. "runtests.py --prebuilt" can take one or more .deb files including these tests, will install them as the "compile" operation and then will use the installed SyncEvolution, without overriding any paths. This relies on having suitable rights for "dpkg" and /usr/lib/syncevolution/test; the way how that is done in the nightly testing is via chroots where the entire file system is writable by the normal test user. Normal users without such write access to /usr/lib/syncevolution/test need to copy that directory into their home directory first.
2013-12-17 09:43:21 +01:00
endif
if ENABLE_TESTING
test_SCRIPTS += \
test/__init__.py \
test/test-dbus.py \
test/testdbus.py \
$(NOP)
# Install symbolic links, to ensure that testing in the testdir
# uses the right SyncEvolution without depending on the PATH.
# client-test should have been installed in testdir already as
# normal executable, see src.am.
all_install_exec_hooks += install-test-files
install-test-files:
mkdir -p $(DESTDIR)/$(testdir)
ln -f -s $(bindir)/syncevolution $(DESTDIR)/$(testdir)
ln -f -s $(bindir)/synccompare $(DESTDIR)/$(testdir)
ln -f -s $(libexecdir)/syncevo-dbus-server $(DESTDIR)/$(testdir)
testing: wait for background daemon in wrappercheck When starting a daemon via wrappercheck, optionally wait for the daemon to write a certain message to its log file. The message is searched for with "grep -e", so regular expressions matching one line are acceptable. Only works in combination with writing that log file. This will be used to wait for syncevo-http-server to confirm that it is running and ready to accept connections.
2014-02-02 19:08:57 +01:00
ln -f -s $(bindir)/synclog2html $(DESTDIR)/$(testdir)
testing: include syncevo-webdav-lookup in test binaries syncevo-webdav-lookup is needed during testing when doing WebDAV database scans, so build it in "src" like the rest of the binaries and link to it in the installed test suite.
2014-07-21 10:19:43 +02:00
ln -f -s $(bindir)/syncevo-webdav-lookup $(DESTDIR)/$(testdir)
testing: wait for background daemon in wrappercheck When starting a daemon via wrappercheck, optionally wait for the daemon to write a certain message to its log file. The message is searched for with "grep -e", so regular expressions matching one line are acceptable. Only works in combination with writing that log file. This will be used to wait for syncevo-http-server to confirm that it is running and ready to accept connections.
2014-02-02 19:08:57 +01:00
cp config.h $(top_srcdir)/src/syncevo/SyncConfig.h src/ClientTest.cpp.html $(DESTDIR)/$(testdir) # needed by test-dbus.py
testing: update packaging and testing of pre-compiled binaries Only the "client-test" executable and its test data were installed so far, in /usr/bin resp. the doc dir. Now also test-dbus.py and testpim.py plus their data files get installed, using a new /usr/lib/syncevolution/test directory for all test files and commands. "runtests.py --prebuilt" can take one or more .deb files including these tests, will install them as the "compile" operation and then will use the installed SyncEvolution, without overriding any paths. This relies on having suitable rights for "dpkg" and /usr/lib/syncevolution/test; the way how that is done in the nightly testing is via chroots where the entire file system is writable by the normal test user. Normal users without such write access to /usr/lib/syncevolution/test need to copy that directory into their home directory first.
2013-12-17 09:43:21 +01:00
all_uninstall_hooks += uninstall-test-files
uninstall-test-files:
rm -f $(DESTDIR)/$(testdir)/syncevolution \
$(DESTDIR)/$(testdir)/synccompare \
$(DESTDIR)/$(testdir)/syncevo-dbus-server \
testing: uninstall synclog2html The test script was installed, but not uninstalled.
2014-07-21 10:18:40 +02:00
$(DESTDIR)/$(testdir)/synclog2html \
testing: include syncevo-webdav-lookup in test binaries syncevo-webdav-lookup is needed during testing when doing WebDAV database scans, so build it in "src" like the rest of the binaries and link to it in the installed test suite.
2014-07-21 10:19:43 +02:00
$(DESTDIR)/$(testdir)/syncevo-webdav-lookup \
testing: update packaging and testing of pre-compiled binaries Only the "client-test" executable and its test data were installed so far, in /usr/bin resp. the doc dir. Now also test-dbus.py and testpim.py plus their data files get installed, using a new /usr/lib/syncevolution/test directory for all test files and commands. "runtests.py --prebuilt" can take one or more .deb files including these tests, will install them as the "compile" operation and then will use the installed SyncEvolution, without overriding any paths. This relies on having suitable rights for "dpkg" and /usr/lib/syncevolution/test; the way how that is done in the nightly testing is via chroots where the entire file system is writable by the normal test user. Normal users without such write access to /usr/lib/syncevolution/test need to copy that directory into their home directory first.
2013-12-17 09:43:21 +01:00
$(DESTDIR)/$(testdir)/SyncConfig.h \
testing: wait for background daemon in wrappercheck When starting a daemon via wrappercheck, optionally wait for the daemon to write a certain message to its log file. The message is searched for with "grep -e", so regular expressions matching one line are acceptable. Only works in combination with writing that log file. This will be used to wait for syncevo-http-server to confirm that it is running and ready to accept connections.
2014-02-02 19:08:57 +01:00
$(DESTDIR)/$(testdir)/ClientTests.cpp.html \
testing: update packaging and testing of pre-compiled binaries Only the "client-test" executable and its test data were installed so far, in /usr/bin resp. the doc dir. Now also test-dbus.py and testpim.py plus their data files get installed, using a new /usr/lib/syncevolution/test directory for all test files and commands. "runtests.py --prebuilt" can take one or more .deb files including these tests, will install them as the "compile" operation and then will use the installed SyncEvolution, without overriding any paths. This relies on having suitable rights for "dpkg" and /usr/lib/syncevolution/test; the way how that is done in the nightly testing is via chroots where the entire file system is writable by the normal test user. Normal users without such write access to /usr/lib/syncevolution/test need to copy that directory into their home directory first.
2013-12-17 09:43:21 +01:00
$(DESTDIR)/$(testdir)/config.h \
$(NOP)
test_DATA += \
test/Makefile \
$(NOP)
nobase_testparent_DATA += \
autotools: avoid redundancy in installation of test files testcase files used to be installed in src/testcases.am, using a duplicated list of files. Better do it in test/test.am with the canonical list of files and only install generated files in src/testcases.am. This makes it easier to extend the list in the future.
2014-05-16 09:44:52 +02:00
$(test_testcases) \
testing: update packaging and testing of pre-compiled binaries Only the "client-test" executable and its test data were installed so far, in /usr/bin resp. the doc dir. Now also test-dbus.py and testpim.py plus their data files get installed, using a new /usr/lib/syncevolution/test directory for all test files and commands. "runtests.py --prebuilt" can take one or more .deb files including these tests, will install them as the "compile" operation and then will use the installed SyncEvolution, without overriding any paths. This relies on having suitable rights for "dpkg" and /usr/lib/syncevolution/test; the way how that is done in the nightly testing is via chroots where the entire file system is writable by the normal test user. Normal users without such write access to /usr/lib/syncevolution/test need to copy that directory into their home directory first.
2013-12-17 09:43:21 +01:00
test/test-dbus/templates/templates/clients/phone/nokia/S40/7210c.ini \
test/test-dbus/templates/templates/clients/SyncEvolution.ini \
test/test-dbus/auto-sync/config/syncevolution/.internal.ini \
test/test-dbus/auto-sync/config/syncevolution/default/.internal.ini \
test/test-dbus/auto-sync/config/syncevolution/default/config.ini \
test/test-dbus/auto-sync/config/syncevolution/default/peers/scheduleworld/.internal.ini \
test/test-dbus/auto-sync/config/syncevolution/default/peers/scheduleworld/config.ini \
test/test-dbus/auto-sync/config/syncevolution/config.ini \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/todo.after.ini \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/todo.current/1 \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/addressbook.before.ini \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/calendar.before.ini \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/todo.current.ini \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/memo.current.ini \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/memo.after/1 \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/memo.after/2 \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/status.ini \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/memo.before/1 \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/todo.after/1 \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/addressbook.current/1 \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/calendar.after.ini \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/calendar.after/1 \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/calendar.after/3 \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/calendar.after/2 \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/memo.after.ini \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/memo.before.ini \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/addressbook.current.ini \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/addressbook.after/1 \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/memo.current/1 \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/memo.current/2 \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/addressbook.after.ini \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/calendar.before/1 \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/calendar.before/3 \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/calendar.before/2 \
test/test-dbus/restore/cache/syncevolution/dummy_+test-2009-12-21-13-19/todo.before.ini \
test/test-dbus/reports/cache/syncevolution/dummy_+test-2009-11-18-12-57/status.ini \
test/test-dbus/reports/cache/syncevolution/dummy-2009-11-18-13-00/status.ini \
test/test-dbus/reports/cache/syncevolution/dummy_+test-2009-11-18-12-55/status.ini \
test/test-dbus/reports/cache/syncevolution/dummy_+test-2009-11-18-13-01/status.ini \
test/test-dbus/reports/cache/syncevolution/dummy_+test-2009-11-18-12-59/status.ini \
test/test-dbus/reports/cache/syncevolution/dummy_+test-2009-11-18-12-58/status.ini \
test/test-dbus/reports/cache/syncevolution/dummy_+test@context-2010-01-20-10-10/status.ini \
test/test-dbus/reports/cache/syncevolution/dummy__test-2009-11-18-12-56/status.ini \
$(NOP)
endif # ENABLE_TESTING
Reference in a new issue Copy permalink