abjugard / dat255-epiclock Goto Github PK

Expected behaviour:
If another alarm activates while the last ones activity is still running, then no new activity is spawned

Actual behaviour:
When the second alarm activates, another activity is spawned in the background, and with it, sound and vibration

Expected behaviour:
When editing an alarm, the create alarm dialogue that is opened should be populated with the old settings.

Actual behaviour:
The module dropdown isn't pre-selected as it should be.

Expected: While editing an alarm the application tells me that I am editing an alarm
What happens: While editing an alarm the application says I am creating an alarm

When an alarm is set and the phone is locked, the application doesn't wake up the phone when the alarm activates.

Example:
Input: Alarm is set at hh:mm
User interact: Locks phone
Output: Phone starts the alarmtone and vibration, but doesn't wake up the phone.

Expected Output: Phone wake up, shows the ActivationActivity view and start the alarmtone and vibration.

After Completing the mathtask the equation for a new problem appears for a short while before the window closes.

Example:
Input: User completes enough problems in a row.
Output: A new equation appears for a while on the screen

Expected Output: The window closes without showing a new problem

Expected behavior:
The sound should always be on when the alarm is activated.

Actual behavior:
The sound is silenced and only the vibration is on when directly after the alarm is activated.

The user is able to lower the volume of the alarm before the task is completed

Expected behaviour:
When an alarm task is completed, the device should return to whatever activity was active prior to the alarm activity spawning

Actual behaviour:
When an alarm task is completed, the Alarmed application main activity is shown

See Acceptance Test #7.3 for expected behavior flow.

Expected behaviour:
If no settings for them have been entered, a newly created alarm should trigger both vibration and sound when alarm goes off

Actual behaviour:
Only sound is triggered when the alarm goes off

For more information see Acceptance Test#10.2

When an alarm has been scheduled an notification if created that shows the time that the alarm will trigger, however when the alarm has been triggered and there is no new alarm scheduled the same notification remains with the same time as before.

Ex: An alarm has been triggered at hh:mm
Inadata: hh:(mm). No alarm is scheduled after.
Output: After the alarm has triggerd the same notification shows that was shown when the alarm was triggerd.

Expected: The old notification should be removed.

AlarmController#createAlarm()

Problem:
The method now has five parameter's and in branch sprint5, the method has been further extended with more paramaters.

Recommendation:
Refactor/rewrite the method to use maximum three paramaters and in best case one or two paramaters

Problem:
After setting an alarm to MemoryModule and then editing it and selecting MathModule instead the MemoryModule is still launching.

The text that displays the time until the alarms triggers i behaving wrong when the minute time is one minute passed the current time.

The text comes from AlarmTime:toString() method.

Ex: Current Time is hh:mm
Inadata: hh:(mm-1)
Output: 59 minutes

The problem occurs for all the minutes that is less than the current minute that hour.