From 24c7c0af982524b1df42c54537178442af9b46e0 Mon Sep 17 00:00:00 2001
From: vadimt <vadimt@google.com>
Date: Mon, 22 Apr 2019 14:07:23 -0700
Subject: [PATCH] Verifying that test initialization switched to workspace

Change-Id: I4d33f831a6fbb6632dc21d056fb239d9d1dcddd8
---
 tests/src/com/android/launcher3/ui/TaplTestsLauncher3.java | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/tests/src/com/android/launcher3/ui/TaplTestsLauncher3.java b/tests/src/com/android/launcher3/ui/TaplTestsLauncher3.java
index dfb0edf627..5ab8d054bc 100644
--- a/tests/src/com/android/launcher3/ui/TaplTestsLauncher3.java
+++ b/tests/src/com/android/launcher3/ui/TaplTestsLauncher3.java
@@ -119,6 +119,8 @@ public class TaplTestsLauncher3 extends AbstractLauncherUiTest {
         test.waitForLauncherCondition("Launcher didn't start", launcher -> launcher != null);
         test.waitForState("Launcher internal state didn't switch to Home", LauncherState.NORMAL);
         test.waitForResumed("Launcher internal state is still Background");
+        // Check that we switched to home.
+        test.mLauncher.getWorkspace();
     }
 
     // Please don't add negative test cases for methods that fail only after a long wait.