Merge lp:~charlesk/indicator-datetime/lp-1411171-strengthen-recurrence-rule-test-rtm-14.09 into lp:indicator-datetime/rtm-14.09

Proposed by Charles Kerr
Status: Merged
Approved by: Robert Bruce Park
Approved revision: 391
Merged at revision: 391
Proposed branch: lp:~charlesk/indicator-datetime/lp-1411171-strengthen-recurrence-rule-test-rtm-14.09
Merge into: lp:indicator-datetime/rtm-14.09
Diff against target: 34 lines (+11/-2)
2 files modified
src/engine-eds.cpp (+5/-2)
tests/manual (+6/-0)
To merge this branch: bzr merge lp:~charlesk/indicator-datetime/lp-1411171-strengthen-recurrence-rule-test-rtm-14.09
Reviewer Review Type Date Requested Status
dobey (community) Approve
Review via email: mp+246634@code.launchpad.net

Commit message

Fix bug that misidentified repeating alarms as one-time alarms, causing them to be disabled after triggering.

Description of the change

Fix bug that misidentified repeating alarms as one-time alarms, causing them to be disabled after triggering.

=== Change Description

Fix bug that misidentified repeating alarms as one-time alarms, causing them to be disabled after triggering.

trunk MP @ https://code.launchpad.net/~charlesk/indicator-datetime/lp-1411171-strengthen-recurrence-rule-test/+merge/246629

=== MP Checklist

> Are there any related MPs required for this MP to build/function as expected? Please list.

No prerequisites

> Is your branch in sync with latest trunk? (e.g. bzr pull lp:trunk -> no changes)

Yes, for latest rtm-14.09

> Did the code build without warnings?

Yes

> Did the tests run successfully?

Yes

> Did you perform an exploratory manual test run of your code change and any related functionality?

Yes

> If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?

N/A

> What device (or emulator) has your component test plan been executed successfully on?

Krillin 198

> What manual tests are relevant for this MP?

indicator-datetime/disable-one-time-alarms-after-notification

> Did you include a link to the MR Review Checklist Template to make your reviewer's life easier?

https://wiki.ubuntu.com/Process/Merges/Checklists/indicator-datetime

To post a comment you must log in.
Revision history for this message
dobey (dobey) :
review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
=== modified file 'src/engine-eds.cpp'
--- src/engine-eds.cpp 2014-12-08 02:52:50 +0000
+++ src/engine-eds.cpp 2015-01-15 19:48:41 +0000
@@ -534,8 +534,11 @@
534 icalcomponent * icc = nullptr;534 icalcomponent * icc = nullptr;
535 if (e_cal_client_get_object_finish (E_CAL_CLIENT(client), result, &icc, nullptr))535 if (e_cal_client_get_object_finish (E_CAL_CLIENT(client), result, &icc, nullptr))
536 {536 {
537 struct icaltimetype itt = icalcomponent_get_recurrenceid(icc);537 auto rrule_property = icalcomponent_get_first_property (icc, ICAL_RRULE_PROPERTY); // transfer none
538 if (icaltime_is_null_time(itt))538 auto rdate_property = icalcomponent_get_first_property (icc, ICAL_RDATE_PROPERTY); // transfer none
539 const bool is_nonrepeating = (rrule_property == nullptr) && (rdate_property == nullptr);
540
541 if (is_nonrepeating)
539 {542 {
540 g_debug("'%s' appears to be a one-time alarm... adding 'disabled' tag.",543 g_debug("'%s' appears to be a one-time alarm... adding 'disabled' tag.",
541 icalcomponent_as_ical_string(icc));544 icalcomponent_as_ical_string(icc));
542545
=== modified file 'tests/manual'
--- tests/manual 2014-12-08 02:52:50 +0000
+++ tests/manual 2015-01-15 19:48:41 +0000
@@ -56,6 +56,12 @@
56 <dd>Confirm that the alarm notification is shown</dd>56 <dd>Confirm that the alarm notification is shown</dd>
57 <dd>Confirm that the alarm's sound is played while the alarm notification is present</dd>57 <dd>Confirm that the alarm's sound is played while the alarm notification is present</dd>
58 <dd>Confirm that the one-time alarm is disabled after the notification is shown. NOTE: due to a refresh bug in clock-app you may need to refresh its alarms page (by swapping back to the main page, then the alarm page again, this is tracked in #1362341) in order to see the alarm change from enabled to disabled.</dd>58 <dd>Confirm that the one-time alarm is disabled after the notification is shown. NOTE: due to a refresh bug in clock-app you may need to refresh its alarms page (by swapping back to the main page, then the alarm page again, this is tracked in #1362341) in order to see the alarm change from enabled to disabled.</dd>
59 <dt>Create and save an upcoming repeating alarm in ubuntu-clock-app</dt>
60 <dd>Confirm that the alarm icon appears next to the current time in unity's indicator display</dd>
61 <dt>Wait until the alarm time is reached</dt>
62 <dd>Confirm that the alarm notification is shown</dd>
63 <dd>Confirm that the alarm's sound is played while the alarm notification is present</dd>
64 <dd>Confirm that the repeating alarm is not disabled after the notification is shown. NOTE: due to a refresh bug in clock-app you may need to refresh its alarms page (by swapping back to the main page, then the alarm page again, this is tracked in #1362341) in order to see the alarm change from enabled to disabled.</dd>
59</dl>65</dl>
6066
61Test-case indicator-datetime/calendar-event-notification67Test-case indicator-datetime/calendar-event-notification

Subscribers

People subscribed via source and target branches