summaryrefslogtreecommitdiff
path: root/fbdaemon
diff options
context:
space:
mode:
authorSandro Knauß <mail@sandroknauss.de>2014-05-30 16:36:43 (GMT)
committerSandro Knauß <mail@sandroknauss.de>2014-05-30 16:36:43 (GMT)
commit86530763597fae89221c4041a19738b5d1f6d380 (patch)
tree1880a4e637dc73bf0a4b59f476630c2d980f1e54 /fbdaemon
parent1a7f746a31c0aae39d913283426e0e381d8fc750 (diff)
downloadkolab-utils-86530763597fae89221c4041a19738b5d1f6d380.tar.gz
Adding README to get a show instruction, how to use cyrus log files in tests
Diffstat (limited to 'fbdaemon')
-rw-r--r--fbdaemon/tests/README17
1 files changed, 17 insertions, 0 deletions
diff --git a/fbdaemon/tests/README b/fbdaemon/tests/README
new file mode 100644
index 0000000..ecb6154
--- /dev/null
+++ b/fbdaemon/tests/README
@@ -0,0 +1,17 @@
+You can place here cyrus logs, that you can get if you follow the wiki:
+https://wiki.kolab.org/Cyrus_imap_telemetry_logging
+Unfortunatelly this wiki is quite outdated, but with google you'll find the correct path.
+For Debian 7.0 /var/lib/imap/log/<username>/
+
+If you created the directory, you can just do what you whant to do.
+Cyrus will create for every connection a new file.
+You can now use this file inside a test:
+
+ CyrusFakeServer fakeServer;
+ fakeServer.addScenarioFromFile("<newfile>");
+ fakeServer.startAndWait();
+
+ //your test
+
+ QVERIFY(fakeServer.isAllScenarioDone());
+ fakeServer.quit();