SRADA-395: add sleep time in tests before assert

Unstable synchronization causes to fail some unit tests.

Change-Id: I02dd6fd35b5f4ef6a367c14da05944baf1802bc4

diff --git a/org.tizen.dynamicanalyzer.cli/test/src/org/tizen/dynamicanalyzer/cli/manager/TracingProcessManagerTest.java b/org.tizen.dynamicanalyzer.cli/test/src/org/tizen/dynamicanalyzer/cli/manager/TracingProcessManagerTest.java
index 90da018..d43401e 100644 (file)
--- a/org.tizen.dynamicanalyzer.cli/test/src/org/tizen/dynamicanalyzer/cli/manager/TracingProcessManagerTest.java
+++ b/org.tizen.dynamicanalyzer.cli/test/src/org/tizen/dynamicanalyzer/cli/manager/TracingProcessManagerTest.java
@@ -157,7 +157,9 @@ public class TracingProcessManagerTest {
                manager = managerConstructor.newInstance(args, process);
 
                // synchronization barrier
-               while (!reached){}
+               while (!reached) {
+                       Thread.sleep(100);
+               }
 
                // actually manager should already recognize that process stopped
                // because process state should be monitored asynchronously due to the specification
@@ -312,7 +314,9 @@ public class TracingProcessManagerTest {
                manager = managerConstructor.newInstance(args, process);
 
                // synchronization barrier
-               while (!reached) {}
+               while (!reached) {
+                       Thread.sleep(100);
+               }
 
                // actually manager should already recognize that process stopped
                assertTrue(manager.isFinished());