• last updated 8 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Test cornercase encountered in practice: a user claims a timezone different to that of the system and creates a calendar item in various formats

This test currently fails, because when we convert the time between the user and the system timezone, we are too strict and allow only the "long" timestamp format "%Y-%m-%d %H:%M:%S"

Extend test cases

Extend testing of data validation

Test checking for attachments availability by providing explicit package_id

Make sure the cal item notification has at least 1 subscriber

Use a test admin user to run the ics test

Fix typos

Deprecate calendar::assign_permissions, trivial wrapper to the permission api

  1. … 2 more files in changeset.
Deprecate calendar::item::assign_permission, trivial wrapper to the permission api

One can in fact replace the only occurrence by granting the admin permission on the item.

Update tests to demonstrate that the behavior remains the same.

  1. … 1 more file in changeset.
Increase proc coverage

Increase proc coverage

Accomodate the test for downstream, where the notification object depends on whether the calendar is private or not

Localize the notification mode as we do downstream, fix test so that the notification generated internally by calendar::item::new is detected, rather than a dummy one

  1. … 5 more files in changeset.
Detect when permission caching is enabled and flush the permission cache in this case

Increae proc coverage

Increase proc coverage

Increase proc coverage

Increase proc coverage

Increase proc coverage

Increase proc coverage

Increase proc coverage

reduce verbosity, add covered calls in test cases

  1. … 1 more file in changeset.
Fix extra braces

Add 'calendar_basic_api' test case, covering 'calendar::new', 'calendar::delete', 'calendar::rename' and 'calendar::name'