Add comments for Thread.sleep

Author: Justin Yang

iterableapi/src/androidTest/java/com/iterable/iterableapi/IterableNotificationTest.java

@@ -63,6 +63,8 @@ public void testNotificationText() throws Exception {
         IterableNotification iterableNotification = IterableNotification.createNotification(getContext(), notif, Application.class);
         IterableNotification.postNotificationOnDevice(appContext, iterableNotification);
         assertEquals("IterableAPI", iterableNotification.mContentTitle);
+//        It looks like mNotificationManager.notify(iterableNotification.requestCode, iterableNotification.build());
+//        is the culprit here for the flaky tests. This thread is spun up by the android system. Unless we do dependency injection and mock the notificationManager, it'll be hard to make this unflake.
         Thread.sleep(100);
         if (android.os.Build.VERSION.SDK_INT >= android.os.Build.VERSION_CODES.M) {
             Bundle notificationExtras = mNotificationManager.getActiveNotifications()[0].getNotification().extras;
@@ -78,6 +80,8 @@ public void testMessage() throws Exception {
 
         IterableNotification iterableNotification = IterableNotification.createNotification(getContext(), notif1, Application.class);
         IterableNotification.postNotificationOnDevice(appContext, iterableNotification);
+//        It looks like mNotificationManager.notify(iterableNotification.requestCode, iterableNotification.build());
+//        is the culprit here for the flaky tests. This thread is spun up by the android system. Unless we do dependency injection and mock the notificationManager, it'll be hard to make this unflake.
         Thread.sleep(100);
         assertFalse(iterableNotification.iterableNotificationData.getIsGhostPush());
         assertEquals("11111111111111111111111111111111", iterableNotification.iterableNotificationData.getMessageId());
@@ -94,6 +98,8 @@ public void testMessage() throws Exception {
 
         IterableNotification iterableNotification2 = IterableNotification.createNotification(getContext(), notif2, Application.class);
         IterableNotification.postNotificationOnDevice(appContext, iterableNotification2);
+//        It looks like mNotificationManager.notify(iterableNotification.requestCode, iterableNotification.build());
+//        is the culprit here for the flaky tests. This thread is spun up by the android system. Unless we do dependency injection and mock the notificationManager, it'll be hard to make this unflake.
         Thread.sleep(100);
         assertFalse(iterableNotification2.iterableNotificationData.getIsGhostPush());
         assertEquals("22222222222222222222222222222222", iterableNotification2.iterableNotificationData.getMessageId());