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

[Nekhelesh Ramananthan]

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.

[Nicholas Skaggs (nskaggs)]

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?

[Nekhelesh Ramananthan (nik90)]

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

[Nekhelesh Ramananthan (nik90)]

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.