mirror of
https://gitlab.com/davical-project/davical.git
synced 2026-05-18 01:31:21 +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
922 B
Plaintext
42 lines
922 B
Plaintext
#
|
|
# Here we are binding against a collection which is itself a binding
|
|
# bindings, at the same level in the same collection.
|
|
#
|
|
# Before:
|
|
# /user4/boundbase a binding to a collection containing two bindings
|
|
# and a real collection
|
|
#
|
|
# After:
|
|
# /user4/bind2bind is bound to /user4/boundbase, so it should also
|
|
# appear to contain two bindings and a collection
|
|
#
|
|
TYPE=BIND
|
|
AUTH=user4:user4
|
|
|
|
HEADER=User-Agent: Ticket Spec Tests
|
|
HEADER=Content-Type: text/xml; charset="UTF-8"
|
|
HEAD
|
|
|
|
|
|
BEGINDATA
|
|
<?xml version="1.0" encoding="utf-8"?>
|
|
<bind xmlns="DAV:">
|
|
<segment>bind2bind-noslash</segment>
|
|
<href>/caldav.php/user4/boundbase</href>
|
|
</bind>
|
|
ENDDATA
|
|
|
|
URL=http://regression.host/caldav.php/user4/
|
|
|
|
QUERY
|
|
SELECT bind_id,
|
|
bound_source_id,
|
|
length(access_ticket_id),
|
|
parent_container,
|
|
dav_name,
|
|
dav_displayname
|
|
FROM dav_binding
|
|
ORDER BY bind_id
|
|
ENDQUERY
|
|
|