[common][alarm][DPTTIZEN-3165, issue with time of test execution]

-modify: 1 tc

Change-Id: I9a8b1f10c211803cd218902e58d6b94b10c1cd97
Signed-off-by: qunfang.lin <qunfang.lin@samsung.com>

diff --git a/common/tct-alarm-tizen-tests/alarm/AlarmAbsolute_getNextScheduledDate_return_null.html b/common/tct-alarm-tizen-tests/alarm/AlarmAbsolute_getNextScheduledDate_return_null.html
index 2c848c5e03424b58412153db4dea1735ab74fb3b..4661a1a62b9986ac74a75f8a02fb6742b35d0f12 100755 (executable)
--- a/common/tct-alarm-tizen-tests/alarm/AlarmAbsolute_getNextScheduledDate_return_null.html
+++ b/common/tct-alarm-tizen-tests/alarm/AlarmAbsolute_getNextScheduledDate_return_null.html
@@ -50,6 +50,7 @@ test(function () {
     });
 
     var alarm, nextScheduledDate, myDate = new Date();
+    myDate.setSeconds(myDate.getSeconds() + 2);
 
     alarm = new tizen.AlarmAbsolute(myDate);
     tizen.alarm.add(alarm, APPLICATION_ID);