diff options
Diffstat (limited to 'tests')
| -rw-r--r-- | tests/README | 8 | ||||
| -rwxr-xr-x | tests/tests.sh | 6 |
2 files changed, 7 insertions, 7 deletions
diff --git a/tests/README b/tests/README index 406ea8e..a6f9605 100644 --- a/tests/README +++ b/tests/README @@ -1,7 +1,7 @@ -TL;DR: run test_calendar-cli.sh, don't run tests.sh. +TL;DR: do run test_calendar-cli.sh, don't run tests.sh - unless you know what you're doing. -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. +test_calendar-cli.sh will attempt to set up a radicale server and a xandikos server, and run tests.sh towards those two. At least one of those should be installed for the tests to work. It will bind up some hard coded ports on localhost, tests will fail if those ports are already in use. (Oups - xandikos doesn't work very well together with calendar-cli at the moment, so it has been skipped). -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 actual tests are in tests.sh. You'll have to run this one if you want to check compatibility with other calendar servers, but it requires either that the $calendar_cli environmental variable is set, or that some calendar server is configured in .config/calendar.conf. If you choose to run the tests towards some old, existing calendar, then be aware that the test code may eventually delete some historic data from 2010. -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. +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. diff --git a/tests/tests.sh b/tests/tests.sh index fa2ff3d..7f8d136 100755 --- a/tests/tests.sh +++ b/tests/tests.sh @@ -34,7 +34,7 @@ echo "## EVENTS" echo "## testing $calendar_cli" echo "## this is a very simple test script without advanced error handling" -echo "## if this test script doesn't output 'all tests completed' in the end, something went wrong" +echo "## if this test script doesn't output 'ALL TESTS COMPLETED! YAY!' in the end, something went wrong" echo "## Attempting to add an event at 2010-10-09 20:00:00, 2 hours duration" calendar_cli calendar add '2010-10-09 20:00:00+2h' 'testing testing' @@ -46,7 +46,7 @@ calendar_cli calendar add '2010-10-10 20:00:00+01:00' 'testing testing' --set-de uid2=$(echo $output | perl -ne '/uid=(.*)$/ && print $1') [ -n "$uid2" ] || error "got no UID back" -echo "## Attempting to add a past event at 2010-10-11 20:00:00, CET, 3h duration" +echo "## Attempting to add an event at 2010-10-11 20:00:00, CET, 3h duration" calendar_cli calendar add '2010-10-11 20:00:00+01:00+3h' 'testing testing' uid3=$(echo $output | perl -ne '/uid=(.*)$/ && print $1') echo "## OK: Added the event, uid is $uid" @@ -181,4 +181,4 @@ calendar_cli todo --hide-parents --categories scripttest complete calendar_cli todo --hide-parents --categories scripttest list [ -z "$output" ] && echo "## OK: found no tasks now" -echo "## all tests completed" +echo "## ALL TESTS COMPLETED! YAY!" |