summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator_test.cpp
diff options
context:
space:
mode:
authorSergey Nikolaienkov <sergeynv@google.com>2020-12-14 05:50:40 +0000
committerSergey Nikolaienkov <sergeynv@google.com>2020-12-16 10:34:34 +0000
commitecad63042b63a352f35b8660f0410502cdbbfcd4 (patch)
treebf9829d4e7f3b61c3838b6c96b26497bdd08a964 /tools/aapt2/java/JavaClassGenerator_test.cpp
parentdf112354712ed2c46880ad3ddad37b2da1186e16 (diff)
Fix Pip tests after Pip Menu migration to a Window
Instrumentation tests on TVs used to use UiObject2.click() method to interact with UI elements. This was inject input events that would prompt input framework to enable the touch mode on the device. This was wrong as TV devices are not expecting to work in the touch mode. Migration of Pip menu from an Activity to a Window exposed this issue, which caused multiple TV Pip tests to fail. With this CL we change the way we interact with UI: we only are using DPad navigation, which also means that we have to "track" the focused element. Bug: 174818743 Test: atest WMShellFlickerTests:TvPipBasicTest Test: atest WMShellFlickerTests:TvPipMenuTests Test: atest WMShellFlickerTests:TvPipNotificationTests Change-Id: I335f8fd8d9c840f751d207c5e60b6af582118fee
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions