123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081 |
- Feature: caldav
- Scenario: Accessing a not existing calendar of another user
- Given user "user0" exists
- When "admin" requests calendar "user0/MyCalendar" on the endpoint "/remote.php/dav/calendars/"
- Then The CalDAV HTTP status code should be "404"
- And The exception is "Internal Server Error"
- Scenario: Accessing a not shared calendar of another user
- Given user "user0" exists
- Given "admin" creates a calendar named "MyCalendar"
- Given The CalDAV HTTP status code should be "201"
- When "user0" requests calendar "admin/MyCalendar" on the endpoint "/remote.php/dav/calendars/"
- Then The CalDAV HTTP status code should be "404"
- And The exception is "Internal Server Error"
- Scenario: Accessing a not shared calendar of another user via the legacy endpoint
- Given user "user0" exists
- Given "admin" creates a calendar named "MyCalendar"
- Given The CalDAV HTTP status code should be "201"
- When "user0" requests calendar "admin/MyCalendar" on the endpoint "/remote.php/caldav/calendars/"
- Then The CalDAV HTTP status code should be "404"
- And The exception is "Sabre\DAV\Exception\NotFound"
- And The error message is "Calendar with name 'MyCalendar' could not be found"
- Scenario: Accessing a not existing calendar of another user
- Given user "user0" exists
- When "user0" requests calendar "admin/MyCalendar" on the endpoint "/remote.php/dav/calendars/"
- Then The CalDAV HTTP status code should be "404"
- And The exception is "Internal Server Error"
- Scenario: Accessing a not existing calendar of another user via the legacy endpoint
- Given user "user0" exists
- When "user0" requests calendar "admin/MyCalendar" on the endpoint "/remote.php/caldav/calendars/"
- Then The CalDAV HTTP status code should be "404"
- And The exception is "Sabre\DAV\Exception\NotFound"
- And The error message is "Node with name 'MyCalendar' could not be found"
- Scenario: Accessing a not existing calendar of myself
- Given user "user0" exists
- When "user0" requests calendar "admin/MyCalendar" on the endpoint "/remote.php/dav/calendars/"
- Then The CalDAV HTTP status code should be "404"
- And The exception is "Internal Server Error"
- Scenario: Creating a new calendar
- When "admin" creates a calendar named "MyCalendar"
- Then The CalDAV HTTP status code should be "201"
- And "admin" requests calendar "admin/MyCalendar" on the endpoint "/remote.php/dav/calendars/"
- Then The CalDAV HTTP status code should be "207"
- Scenario: Propfind on public calendar endpoint without calendars
- When "admin" creates a calendar named "MyCalendar"
- Then The CalDAV HTTP status code should be "201"
- And "admin" publicly shares the calendar named "MyCalendar"
- Then The CalDAV HTTP status code should be "202"
- When "admin" requests calendar "/" on the endpoint "/remote.php/dav/public-calendars"
- Then The CalDAV HTTP status code should be "207"
- Then There should be "0" calendars in the response body
- Scenario: Create calendar request for non-existing calendar of another user
- Given user "user0" exists
- When "user0" sends a create calendar request to "admin/MyCalendar2" on the endpoint "/remote.php/dav/calendars/"
- Then The CalDAV HTTP status code should be "404"
- And The exception is "Internal Server Error"
- Scenario: Create calendar request for existing calendar of another user
- Given user "user0" exists
- When "admin" creates a calendar named "MyCalendar2"
- Then The CalDAV HTTP status code should be "201"
- When "user0" sends a create calendar request to "admin/MyCalendar2" on the endpoint "/remote.php/dav/calendars/"
- Then The CalDAV HTTP status code should be "404"
- And The exception is "Internal Server Error"
- Scenario: Update a principal's schedule-default-calendar-URL
- Given user "user0" exists
- And "user0" creates a calendar named "MyCalendar2"
- When "user0" updates property "{urn:ietf:params:xml:ns:caldav}schedule-default-calendar-URL" to href "/remote.php/dav/calendars/user0/MyCalendar2/" of principal "users/user0" on the endpoint "/remote.php/dav/principals/"
- Then The CalDAV response should be multi status
- And The CalDAV response should contain a property "{urn:ietf:params:xml:ns:caldav}schedule-default-calendar-URL"
- When "user0" requests principal "users/user0" on the endpoint "/remote.php/dav/principals/"
- Then The CalDAV response should be multi status
- And The CalDAV response should contain a property "{urn:ietf:params:xml:ns:caldav}schedule-default-calendar-URL" with a href value "/remote.php/dav/calendars/user0/MyCalendar2/"
|