Test 1 Create a course, enrol a student Add two assignments, with the following settings: Assign 1 Due date: Tomorrow Submission type: Online text or File upload Assing 2 Due date: The day after tomorrow Submission type: Nothing checked Login as a student Check the timeline block on your dashboard. Confirm that you see "{{Assign 1}" with a link "Add submission" Go to the calendar. Confirm that you see both " Assign 1 " and " Assign 2 ". Open " Assign 1 "'s due date event, confirm that you see " Add submission ". Close the event modal and open " Assign 2 "'s due date event. Confirm that you see "Go to activity" instead. Test 2 (quick regression check) Manually create some events in the calendar (user, course, category, site). Make sure you can edit and delete them following "edit" and "delete" buttons. Make sure you can drag editable events to the different dates and they save Make sure (as a teacher) you can drag the "Assignment due date" event to a different date inside the calendar and it saves, even though it does not display the "Edit" button anywhere Test 3a (plugin support) - Standard event This is an example of creating an event from a plugin (block "Comments"), feel free to improvise to test. Open blocks/comments/block_comments.php and add to the get_content() function global $DB; $instanceid = 11; $ev = $DB->get_record('event', ['component' => 'block_comments', 'eventtype' => 'mytype', 'instance' => $instanceid]); if (!$ev) { $event = new stdClass(); $event->eventtype = 'mytype'; $event->type = CALENDAR_EVENT_TYPE_STANDARD; // Change it to CALENDAR_EVENT_TYPE_ACTION in the next step. $event->name = $event->description = 'Test event ' . $instanceid; $event->instance = $instanceid; $event->timestart = $event->timesort = time() + DAYSECS; $event->visible = 1; $event->timeduration = 0; $event->context = context_system::instance(); $event->component = 'block_comments'; calendar_event::create($event, false); } Add an instance of block "Comments" to any course and view this course page. Now your event will be created. Go to your calendar. Confirm that you see " Test event 11 " and its date is set for tomorrow. View this event in all possible view modes (monthly, daily, upcoming, clicking on the event so it opens in a popup, etc). Make sure that it is always displayed consistently and there are no "Edit" and "Delete" buttons anywhere. Check your timeline on the dashboard. Confirm that this event will not be there (it is not an action event yet) Test 3b (plugin support) - Action event Turn your event into an action event by editing the code snippet in Test 3a: Set " $instanceid " to 12. Set " $event->type " from " CALENDAR_EVENT_TYPE_STANDARD " to " CALENDAR_EVENT_TYPE_ACTION " Refresh the page with the comments block to generate this action event. Go to the calendar. Confirm that you see " Test event 12 " in the calendar. Add this callback to the blocks/comments/lib.php : function block_comments_core_calendar_provide_event_action(calendar_event $event, \core_calendar\action_factory $factory, $userid = 0) { return $factory->create_instance('My action', new \moodle_url('/my'), 5, true); } Check all possible views in the calendar and make sure that " Test event 12 " is displayed with an action link " My action " in the bottom. Confirm that it can still not be edited or deleted. Go to your dashboard and check the timeline block. Confirm sure that " Test event 12 " appears in the timeline Add this callback to the blocks/comments/lib.php : function block_comments_core_calendar_is_event_visible(calendar_event $event, $userid = 0) { return false; } Refresh the dashboard and check the timeline block. Confirm that " Test event 12 " disappeared from the timeline block. Go to the calendar and confirm that it also disappeared from the calendar. Confirm that " Test event 12 " also disappeared from the calendar. Confirm that " Test event 11 " is still present in the calendar (The visibility callback does not affect standard type events) Edit " block_comments_core_calendar_is_event_visible " return from false to true so the action events are displayed again. Add this callback to the blocks/comments/lib.php : function block_comments_core_calendar_event_action_shows_item_count(calendar_event $event, $itemcount = 0) { return true; } Make sure that the item count (5) now shows in the timeline for the action event but it is not shown in the calendar itself Test 4 (even more) Revert code changes from Test 3. git reset --hard origin/master Remove the test events from the mdl_event table manually. Cherry-pick the following test commit. git fetch https://github.com/marinaglancy/moodle MDL-58866-master-test git cherry-pick FETCH_HEAD Purge the caches Refresh the page with the comments block to create the test events. This creates a different type of component event, it is visible not just for current user but for any user (you can test it). Confirm that you see Test event 13 (standard event) in the calendar but not on the timeline block events in the calendar. Confirm that you see the Test event 14 (action event) on both the timeline block and the calendar. Make sure the icon for this new event is custom and it has the alt-text from the language string ("My event type") After the test, make sure to revert the test commit with the git command on step 1.