summaryrefslogtreecommitdiff
path: root/tests
diff options
context:
space:
mode:
authorTobias Brox <tobias@redpill-linpro.com>2022-11-24 00:36:52 +0100
committerTobias Brox <tobias@redpill-linpro.com>2022-11-24 00:36:52 +0100
commit50dd36f46db83b476b4d2cbbdf62f3982ffe3e2d (patch)
treee101a4a05013c79a7ee328d1e0860fee3301f5e4 /tests
parent891359b85d305199a76283f412107359e8674b7d (diff)
downloadcalendar-cli-50dd36f46db83b476b4d2cbbdf62f3982ffe3e2d.zip
preparing for v0.14.0-release
Diffstat (limited to 'tests')
-rw-r--r--tests/README2
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/README b/tests/README
index a6f9605..6d78bf2 100644
--- a/tests/README
+++ b/tests/README
@@ -4,4 +4,4 @@ test_calendar-cli.sh will attempt to set up a radicale server and a xandikos ser
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.
-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.
+Probably we should add some standard python test code here that can be run through pytest and/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.