summaryrefslogtreecommitdiff
path: root/tests/README
diff options
context:
space:
mode:
authorTobias Brox <tobias@redpill-linpro.com>2020-06-05 01:15:38 +0200
committerTobias Brox <tobias@redpill-linpro.com>2020-06-05 01:15:38 +0200
commit202825548178e61e2abc0d956ae386bb250cc919 (patch)
tree77e03a2813997169389d63675083d9e37e2430cd /tests/README
parent863bf6f280d6d714c46deb55c93e99106083e8cc (diff)
downloadcalendar-cli-202825548178e61e2abc0d956ae386bb250cc919.zip
make it possible to create a calendar, resolves https://github.com/tobixen/calendar-cli/issues/69 - automated tests towards radicale, ref https://github.com/tobixen/calendar-cli/issues/68
Diffstat (limited to 'tests/README')
-rw-r--r--tests/README7
1 files changed, 7 insertions, 0 deletions
diff --git a/tests/README b/tests/README
new file mode 100644
index 0000000..406ea8e
--- /dev/null
+++ b/tests/README
@@ -0,0 +1,7 @@
+TL;DR: run test_calendar-cli.sh, don't run tests.sh.
+
+Probably we should add some standard python test code here that can be run through nose or tox, but after all this is a command line utility - hence I found it appropriate to start with functional tests written to be executed from through a shell.
+
+The file tests.sh will run towards whatever calendar server is configured in .config/calendar.conf, and it has potential side effects, it will wipe out any prior events within the time range 2010-10-10 and 2010-10-14.
+
+The file test_calendar-cli.sh will set up a radicale calendar server, run the tests.sh towards radicale, then set up xandikos and run tests.sh towards xandikos.