commit faf4da386d312a7db66b31e42a19aa397e6218e6
author vadimt <vadimt@google.com> Mon May 04 15:40:47 2020 -0700
committer vadimt <vadimt@google.com> Mon May 04 15:40:47 2020 -0700
tree db6b1ade21d7a1b39d479d71f1cf1e523ccf8045
parent 0dbbd8951da6822568a30d226275166861620128

Speeding up TAPL by calling getVisibleStateMessage() less frequently

The information in the message can be derived from the object dump
printed anyways.

Change-Id: I22ee136568b767c3218eaabc3920c77b3ceaa78f

tests/tapl/com/android/launcher3/tapl/LauncherInstrumentation.java

diff --git a/tests/tapl/com/android/launcher3/tapl/LauncherInstrumentation.java b/tests/tapl/com/android/launcher3/tapl/LauncherInstrumentation.java
index 085df74..938be2e 100644
--- a/tests/tapl/com/android/launcher3/tapl/LauncherInstrumentation.java
+++ b/tests/tapl/com/android/launcher3/tapl/LauncherInstrumentation.java
@@ -651,7 +651,7 @@
                 } else {
                     log("Hierarchy before swiping up to home:");
                     dumpViewHierarchy();
-                    log(action = "swiping up to home from " + getVisibleStateMessage());
+                    action = "swiping up to home";
 
                     try (LauncherInstrumentation.Closable c = addContextLayer(action)) {
                         swipeToState(
@@ -666,7 +666,7 @@
             } else {
                 log("Hierarchy before clicking home:");
                 dumpViewHierarchy();
-                log(action = "clicking home button from " + getVisibleStateMessage());
+                action = "clicking home button";
                 try (LauncherInstrumentation.Closable c = addContextLayer(action)) {
                     mDevice.waitForIdle();