mirror of
https://gitlab.com/davical-project/davical.git
synced 2026-05-19 01:34:26 +00:00
7c47658bee
This allows us to have more complex test files where an action is taken, then we test something, then another action is taken, etc. Changes to test files are required so that URL is defined after all the required settings are set. Changes to the result files are either whitespace changes due to above logic changes, or printing out a SQL Result header before each result. I figured it was useful.
42 lines
1.2 KiB
Plaintext
42 lines
1.2 KiB
Plaintext
#
|
|
# Create a recurring event, ensure we can fetch future events.
|
|
# To test: https://gitlab.com/davical-project/davical/-/issues/268
|
|
#
|
|
TYPE=PUT
|
|
HEADER=Content-Type: text/calendar
|
|
HEAD
|
|
|
|
|
|
BEGINDATA
|
|
BEGIN:VCALENDAR
|
|
VERSION:2.0
|
|
PRODID:-//davical.org//NONSGML AWL Calendar//EN
|
|
CALSCALE:GREGORIAN
|
|
BEGIN:VTIMEZONE
|
|
TZID:America/New_York
|
|
END:VTIMEZONE
|
|
BEGIN:VEVENT
|
|
SUMMARY:Repeating event
|
|
UID:complex-rrule-issue268
|
|
DTSTART;TZID=America/New_York:20220720T091000
|
|
RRULE:FREQ=MINUTELY;INTERVAL=15;BYDAY=MO,TU,WE,TH,FR;BYHOUR=9,10
|
|
,11,12,13,14,15,16
|
|
END:VEVENT
|
|
END:VCALENDAR
|
|
ENDDATA
|
|
|
|
URL=http://regression.host/caldav.php/user1/home/complex-rrule-issue268.ics
|
|
|
|
QUERY
|
|
SELECT caldav_data.user_no, caldav_data.dav_etag, caldav_type, logged_user,
|
|
uid, dtstart at time zone olson_name as dtstart,
|
|
dtend at time zone olson_name as dtend, due, summary, location,
|
|
description, priority, class, transp, rrule, url,
|
|
percent_complete, tz_id, status,
|
|
caldav_data AS " CalDAV Data",
|
|
dtend - dtstart AS "~Duration"
|
|
FROM caldav_data JOIN calendar_item USING(dav_name) JOIN timezones ON (tz_id=tzid)
|
|
WHERE caldav_data.dav_name =
|
|
'/user1/home/complex-rrule-issue268.ics';
|
|
ENDQUERY
|