diff --git a/test-cases/apertis-update-manager-ota-api.yaml b/test-cases/apertis-update-manager-ota-api.yaml
index 175b61100f8352108789e1eafbdd5a3791be0864..077727371abd36288ebaa48429797a2c2ea5a595 100644
--- a/test-cases/apertis-update-manager-ota-api.yaml
+++ b/test-cases/apertis-update-manager-ota-api.yaml
@@ -11,6 +11,16 @@ metadata:
   maintainer: "Apertis Project"
   description: "Test the apertis-update-manager API for updates over the air."
 
+  pre-conditions:
+    - >
+      This test requires a properly configured time source: when testing
+      devices not carrying a battery-backed real time clock in a network which
+      prevents connections to NTP servers (and only in that case) manually
+      ensure that the time on the device is set appropriately and that it is
+      propagated to the hardware clock so it is stay set on the next reboot if
+      the power is not plugged off.
+    - $ sudo timedatectl --adjust-system-clock set-time "2019-08-21 18:49:03" # use the appropriate date
+
   resources:
     - "The DUT u-boot environment must be clean: in u-boot, run: `env default -a` followed by `saveenv`"
     - "A PC must be connected to DUT serial port"
diff --git a/test-cases/apertis-update-manager-ota-diskfull.yaml b/test-cases/apertis-update-manager-ota-diskfull.yaml
index 6fc2c48f6d176b58970bd3833648748256748e29..87b87738ee074770fce9f64900dfc01528d66585 100644
--- a/test-cases/apertis-update-manager-ota-diskfull.yaml
+++ b/test-cases/apertis-update-manager-ota-diskfull.yaml
@@ -11,6 +11,16 @@ metadata:
   maintainer: "Apertis Project"
   description: "Ensure that failures due to disk full errors during network updates have no effect on the system"
 
+  pre-conditions:
+    - >
+      This test requires a properly configured time source: when testing
+      devices not carrying a battery-backed real time clock in a network which
+      prevents connections to NTP servers (and only in that case) manually
+      ensure that the time on the device is set appropriately and that it is
+      propagated to the hardware clock so it is stay set on the next reboot if
+      the power is not plugged off.
+    - $ sudo timedatectl --adjust-system-clock set-time "2019-08-21 18:49:03" # use the appropriate date
+
   resources:
     - "The DUT u-boot environment must be clean: in u-boot, run: `env default -a` followed by `saveenv`"
     - "A PC must be connected to DUT serial port"
diff --git a/test-cases/apertis-update-manager-ota-rollback.yaml b/test-cases/apertis-update-manager-ota-rollback.yaml
index 9f032b2afdb6158e0b2b2493f8bbf439880e434b..3df3ac9e3d9a72f0c0c5b37fa9c974b1f8c32760 100644
--- a/test-cases/apertis-update-manager-ota-rollback.yaml
+++ b/test-cases/apertis-update-manager-ota-rollback.yaml
@@ -11,6 +11,16 @@ metadata:
   maintainer: "Apertis Project"
   description: "Test the automatic rollback and blacklist mechanism of apertis-update-manager with network updates."
 
+  pre-conditions:
+    - >
+      This test requires a properly configured time source: when testing
+      devices not carrying a battery-backed real time clock in a network which
+      prevents connections to NTP servers (and only in that case) manually
+      ensure that the time on the device is set appropriately and that it is
+      propagated to the hardware clock so it is stay set on the next reboot if
+      the power is not plugged off.
+    - $ sudo timedatectl --adjust-system-clock set-time "2019-08-21 18:49:03" # use the appropriate date
+
   resources:
     - "The DUT u-boot environment must be clean: in u-boot, run: `env default -a` followed by `saveenv`"
     - "A PC must be connected to DUT serial port"
diff --git a/test-cases/apertis-update-manager-ota-signed.yaml b/test-cases/apertis-update-manager-ota-signed.yaml
index ac7df817a9f4a97e68b0e2f268fc03ba0a49edc4..3ca998eaba516a3bcb9a18065a6d8baabdbddf99 100644
--- a/test-cases/apertis-update-manager-ota-signed.yaml
+++ b/test-cases/apertis-update-manager-ota-signed.yaml
@@ -11,6 +11,16 @@ metadata:
   maintainer: "Apertis Project"
   description: "Test the apertis-update-manager uses only signed updates over the air."
 
+  pre-conditions:
+    - >
+      This test requires a properly configured time source: when testing
+      devices not carrying a battery-backed real time clock in a network which
+      prevents connections to NTP servers (and only in that case) manually
+      ensure that the time on the device is set appropriately and that it is
+      propagated to the hardware clock so it is stay set on the next reboot if
+      the power is not plugged off.
+    - $ sudo timedatectl --adjust-system-clock set-time "2019-08-21 18:49:03" # use the appropriate date
+
   resources:
     - "The DUT u-boot environment must be clean: in u-boot, run: `env default -a` followed by `saveenv`"
     - "A PC must be connected to DUT serial port"