davical/testing/tests/regression-suite/0702-caldav4j-PUT.test
Andrew Ruthven 7c47658bee Make the curl and SQL requests when we see them
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.
2024-04-01 22:57:10 +13:00

59 lines
1.4 KiB
Plaintext

#
# PUT an caldav4j regression testing event into the database
#
# Note that although this event appears to refer to the NY time
# zone it does not reference it, since DTSTART/DTEND are VALLUE=DATE
# which may not reference a timezone.
#
TYPE=PUT
HEADER=Content-Type: text/calendar
HEADER=User-Agent: Jakarta Commons-HttpClient/3.0
HEAD
BEGINDATA
BEGIN:VCALENDAR
PRODID:-//OSAF//NONSGML Scoooby Server//EN
VERSION:2.0
CALSCALE:GREGORIAN
BEGIN:VTIMEZONE
TZID:America/New_York
LAST-MODIFIED:20051220T211408Z
BEGIN:STANDARD
DTSTART:20051030T060000
TZOFFSETTO:-0500
TZOFFSETFROM:+0000
TZNAME:EST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20060402T010000
TZOFFSETTO:-0400
TZOFFSETFROM:-0500
TZNAME:EDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;VALUE=DATE:20060101
DTEND;VALUE=DATE:20060102
SUMMARY:All_Day_NY_JAN1
UID:C68DADAD-37CE-44F7-8A37-52E1D02E29CA
SEQUENCE:4
DTSTAMP:20090515T095326Z
END:VEVENT
END:VCALENDAR
ENDDATA
URL=http://regression.host/caldav.php/user1/collection/All_Day_NY_JAN1.ics
QUERY
SELECT caldav_data.user_no, caldav_data.dav_etag, caldav_type, logged_user,
uid, dtstamp, dtstart, dtend, due, summary, location,
description, priority, class, transp, rrule, url,
percent_complete, tz_id, status,
caldav_data AS " CalDAV Data", calendar_item.last_modified
FROM caldav_data LEFT JOIN calendar_item USING(dav_name) LEFT JOIN timezones ON (tz_id=tzid)
WHERE caldav_data.dav_name =
'/user1/collection/All_Day_NY_JAN1.ics'
ENDQUERY