nightly testing: renamed ical20/itodo20/vcard30/text, removed vcard21 from Evolution backend (BMC #14972)

The distinction between vcard21 and vcard30 became mute in the Evolution
backend a while ago. Both tests ended up using the vCard 3.0 Evolution
tests data and the default uri for each server. This patch removes
the vCard 2.1 special case.

It also renames the tests and test data to reflect that they always
were Evolution specific. The new naming convention, also applied
to file, QtContacts, KCalExtended, XMLRPC, Maemo and Akonadi backends, is
now <backend>_contact/event/task/memo, with eds/file/qt/kcal/maemo/kde
as backend names.

The reasoning is:
- results in unique string (in particular no overlap with
  backend type names), easier to search for
- underscore already used before (in contrast to hyphen)
- no plural-s to keep the name shorter

The Akonadi backend should be using its own test data instead of
the Evolution ones.

1 files changed, 7 insertions, 4 deletions

diff --git a/HACKING b/HACKING
index 0021fc61..5ae16fea 100644
--- a/HACKING
+++ b/HACKING
@@ -139,7 +139,10 @@ then run "src/client-test" as described in src/client-test-app.cpp.
 It understands several environment variables, among them:
 - CLIENT_TEST_SERVER = chooses config
 - CLIENT_TEST_SOURCES = comma separated list of enabled sources, identified
-  by their name (ical20, vcard21, vcard30, itodo20, text (= memos))
+  by their name
+  For Evolution: eds_contact,eds_event,eds_task,eds_memo
+  For file backend: file_contact,file_event,file_task,file_memo (uses same test
+  data and vCard flavor as Evolution)
 - CLIENT_TEST_EVOLUTION_PREFIX=[name|file://<path>] overrides
   the evolutionsource setting in the configuration; if file:// is used
   then these database will be created automatically
@@ -361,7 +364,7 @@ SyncEvolution enables Buteo testing based client-test. Configure with
 "src/client-test" to test Buteo with the above described environment
 variables. The only difference is that you have to set a new one
 "CLIENT_TEST_BUTEO=1". Buteo testing supports testing two kinds of
-data: qt_vcard30 and kcal_ical20.
+data: qt_contact and kcal_event.
 
 Here are step-by-step instructions to get started with Buteo testing,
 also using ScheduleWorld as example:
@@ -377,5 +380,5 @@ also using ScheduleWorld as example:
   => change the access mode of the directory /etc/sync
 - CLIENT_TEST_SERVER=scheduleworld \
   CLIENT_TEST_EVOLUTION_PREFIX=file:///tmp/testing/ \
-  ./client-test Client::Sync::qt_vcard30
-  => runs all tests for qt_vcard30
+  ./client-test Client::Sync::qt_contact
+  => runs all tests for qt_contact