This is a risky business, as we can be broken by platform changes like:
b/118891218
Note that TAPL itself still uses pressing Home button.
Change-Id: I55772622fac5f19f6c9f19716a185bbfdbf602a9
These tests call sendPointer() which fails with
"Injecting to another application requires INJECT_EVENTS permission".
Will re-add them later.
Test: running those in OOP and in-proc
Change-Id: I1c96fad14cf8bef896209a94065614a6207ea751
Moving some tests to TaplTests. It's a right idea in general, also
flakes seem to go away because of a different initialization pattern.
Reintroducing UIDevice.pressHome in the test's start. Once BVTs pass,
I'll switch back.
See b/121335479
Test: All nexus tests
Change-Id: I677be5b6aaf073d15e8f2cf9b7a940a1f457b325
The hope is that this will solve flakiness of widgets tests in AOSP.
Test: TaplTestsLauncher3.testWidgets
Change-Id: I2ecc18b9eb7eeb3fd8b11fcc580a529f545c3af9
On the AOSP target, there are not enough apps to make App Apps
scrollable. Moving the test to QS Tapl tests.
Change-Id: I95e196bafdbd0fee77705554890a7c3cda7ac92a
Tests: the affected test
More precisely, an experiment on whether this will help. The theory is
that the current implementation where we long-press an icon for a fixed
period of time sometimes doesn't work because Launcher might start
measuring the press time with some delay.
Now we keep pressed the icon until the menu appears.
Change-Id: I1cead505726a998316a73d81b10160517f17f08f
Tests:ShortcutsToHomeTest.testDragIcon
This will allow running as many as possible automatic checks on AOSP
launcher and moving most AOSP tests that use TAPL to where they belong
to: Tapl Tests.
Bug: 110103162
Test: Running the test suites
Change-Id: I9192354e6097698d4b942c5682b79664ecc2336d
The tests mistakenly took the caption (if on top) as the first context
menu item.
Change-Id: Ibd3264814f2c818742ab164503bf7136fedcde31
Tests: com.android.launcher3.ui.ShortcutsToHomeTest
Doing so by not letting any events between XXX:enter and XXX:exit
events. This eliminates unnecessary permutations.
Example: 2 threads with 3 enter-exit pairs each would have produced 924
permutations before this, now only 20.
Bug: 120628042
Change-Id: Ia243d273a1d90202011679cc7520ea4c9e43918b
Tests: All tests that use race condition framework
It may change (say from 'need to choose' or 'nexus launcher' to
launcher3) during the test execution.
Test: Launcher3:com.android.launcher3.ui.AllAppsIconToHomeTest, fallback recents, TaplTests
Change-Id: I529dd5e28749012731af05edd0adaa4b7d205581
This would guaranteed to repro b/118441555 before it was fixed.
The test doesn't use the most powerful feature of race condition
reproducer, which is enumerating all possible event sequences.
Instead, it uses explicit repro sequences, which makes the test much
faster.
Bug: 120628042
Test: The added test
Change-Id: I89a7a9964f160a8a20ba3d9dda2f248237713014
Hyunyoung Song
Vadim Tryshev
Sunny Goyal
TreeHugger Robot