Ubuntu Clock App

Alarms AP tests need to cleanup alarms after the test is complete

Bug #1283031 reported by Nekhelesh Ramananthan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Clock App
Triaged
Medium
Unassigned
Ubuntu Clock App 3.x.backlog "uncategorized"

Bug Description

Currently the autopilot test cleans up timers and world clocks created during the AP tests by creating a test U1dB database. However it doesn't take that into account for alarms since alarms use EDS for alarm storage. As a result the AP tests could pollute the test environment (Jenkins or user) alarm database.

Either the alarm test should add a delete_alarm statement when they finish or a separate EDS collection be created while running the alarms test db.

Revision history for this message
Nicholas Skaggs (nskaggs) wrote :

EDS data (like alarms) is in ~/.local/share/evolution/, but we can't go playing in that sandbox directly :-) We should mock home completely yes?

Revision history for this message
Nekhelesh Ramananthan (nik90) wrote :

Let's revisit this bug in the 14.10 cycle as we don't have anymore for 14.10.

Changed in ubuntu-clock-app:
milestone: 1.8 → backlog
Nekhelesh Ramananthan (nik90)
Changed in ubuntu-clock-app:
milestone: backlog → alarm-blockers
Nekhelesh Ramananthan (nik90)
Changed in ubuntu-clock-app:
milestone: alarm-blockers → rtm
Revision history for this message
Nekhelesh Ramananthan (nik90) wrote :

I had a discussion with charles and zsombor about this and post-rtm the alarm backend will switch from EDS to Json based backend which should be much easier to mock (similar to clock app settings). We will revisit this bug then.

Changed in ubuntu-clock-app:
milestone: rtm → postrtm
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.