diff options
author | Tobias Brox <tobias@redpill-linpro.com> | 2022-09-30 01:29:58 +0200 |
---|---|---|
committer | Tobias Brox <tobias@redpill-linpro.com> | 2022-10-09 01:55:25 +0200 |
commit | e9a968157e65e18d1b285a7765ecb641175ba370 (patch) | |
tree | 4c770db41f5effaa79447df59023b536a5a60738 /tests/tests.sh | |
parent | fd834cd17933bad5567f1315ddc800145081dcd6 (diff) | |
download | calendar-cli-e9a968157e65e18d1b285a7765ecb641175ba370.zip |
More work on the kal aka cal.py command. It can now do around 80% of all the stuff calendar-cli can do, plus more.
Diffstat (limited to 'tests/tests.sh')
-rwxr-xr-x | tests/tests.sh | 10 |
1 files changed, 3 insertions, 7 deletions
diff --git a/tests/tests.sh b/tests/tests.sh index bd1fbfb..1c91270 100755 --- a/tests/tests.sh +++ b/tests/tests.sh @@ -22,7 +22,6 @@ then echo "This script will use the following commands to access a calendar server:" echo echo "$calendar_cli" - echo "$kal" echo echo "This may work if you have configured a calendar server." echo "The tests will add and delete events and tasks." @@ -77,7 +76,7 @@ echo "## Deleting events with uid $uid $uid1 $uid2" calendar_cli calendar delete --event-uid=$uid calendar_cli calendar delete --event-uid=$uid2 calendar_cli calendar delete --event-uid=$uid3 -kal select --uid=$uid3 delete + echo "## Searching again for the deleted event" calendar_cli calendar agenda --from-time=2010-10-10 --agenda-days=3 echo $output | { grep -q 'testing testing' && error "still found the event" ; } || echo "## OK: didn't find the event" @@ -103,7 +102,7 @@ echo "## cleanup, delete it" calendar_cli calendar delete --event-uid=$uid echo "## Same, using kal add ics" -kal add ical --ical-file=$tmpfile +calendar_cli calendar addics --file $tmpfile rm $tmpfile calendar_cli --icalendar calendar agenda --from-time=2010-10-13 --agenda-days=1 @@ -115,8 +114,6 @@ echo "## cleanup, delete it" calendar_cli calendar delete --event-uid=$uid ## TODO - procrastinated, waiting for response on https://github.com/dateutil/dateutil/issues/1184 -#echo "## Same, using kal add event" -#kal add event '2010-10-10+4d' 'whole day testing' #uid=$(echo $output | perl -ne '/uid=(.*)$/ && print $1') #[ -n "$uid" ] || error "got no UID back" #calendar_cli --icalendar calendar agenda --from-time=2010-10-13 --agenda-days=1 @@ -184,7 +181,7 @@ echo "## TODOS / TASK LISTS" echo "## Attempting to add a task with category 'scripttest'" calendar_cli todo add --set-categories scripttest "edit this task" uidtodo1=$(echo $output | perl -ne '/uid=(.*)$/ && print $1') -kal add --set-categories scripttest todo "edit this task2" +calendar_cli todo add --set-categories scripttest todo "edit this task2" uidtodo2=$(echo $output | perl -ne '/uid=(.*)$/ && print $1') echo "## Listing out all tasks with category set to 'scripttest'" @@ -193,7 +190,6 @@ calendar_cli todo --categories scripttest list echo "## Editing the task" calendar_cli todo --categories scripttest edit --set-summary "editing" --add-categories "scripttest2" -#kal select --todo --categories scripttest edit --add-categories "scripttest3" echo "## Verifying that the edits got through" calendar_cli todo --categories scripttest list |