mirror of
https://gitlab.com/davical-project/davical.git
synced 2026-01-27 00:33:34 +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.
45 lines
1.2 KiB
Plaintext
45 lines
1.2 KiB
Plaintext
#
|
|
# Check for support of PROPPATCH method
|
|
#
|
|
# Adding the 'owner' property to a collection
|
|
#
|
|
TYPE=PROPPATCH
|
|
HEADER=User-agent: SpecTest PROPPATCH
|
|
HEADER=Content-type: text/xml
|
|
HEAD
|
|
|
|
BEGINDATA
|
|
<?xml version="1.0" encoding="utf-8" ?>
|
|
<propertyupdate xmlns="DAV:" xmlns:X="urn:mcmillan:bogus:xml:ns:davical">
|
|
<set>
|
|
<prop>
|
|
<X:arbitrary>A completely bogus property which should be saved.</X:arbitrary>
|
|
<displayname>User One's Not Calendar</displayname>
|
|
</prop>
|
|
</set>
|
|
<remove>
|
|
<prop>
|
|
<resourcetype>
|
|
<calendar xmlns="urn:ietf:params:xml:ns:caldav"/>
|
|
</resourcetype>
|
|
</prop>
|
|
</remove>
|
|
</propertyupdate>
|
|
ENDDATA
|
|
|
|
URL=http://regression.host/caldav.php/user1/home/
|
|
|
|
QUERY
|
|
SELECT dav_displayname, is_calendar, resourcetypes,
|
|
modified > (current_timestamp - '120 seconds'::interval) AS changed_recently
|
|
FROM collection WHERE dav_name = '/user1/home/' ORDER BY collection_id
|
|
ENDQUERY
|
|
|
|
QUERY
|
|
SELECT dav_name, property_name, property_value, changed_by,
|
|
changed_on > (current_timestamp - '120 seconds'::interval) AS changed_recently
|
|
FROM property
|
|
WHERE dav_name = '/user1/home/'
|
|
ORDER BY dav_name, property_name
|
|
ENDQUERY
|