1. Skip all tests that fail in inproc mode on CF (this CL)
2. Observe postsubmit and make sure no inproc tests are failing or too
flaky on CF
3. Enable presubmit
4. Switch to skipping tests from step 1 only for inproc presubmit;
they'll start failing in postsubmit
5. Gradually make all tests pass and not flaky and enable them back on
presubmit
Bug: 142828227
Change-Id: I0092d6b92b0358866f8cbf9e00dbe3fabe23703d
The plan:
1. Skip all tests that fail in inproc mode on CF (this CL)
2. Observe postsubmit and make sure no inproc tests are failing or too
flaky on CF
3. Enable presubmit
4. Switch to skipping tests from step 1 only for inproc presubmit;
they'll start failing in postsubmit
5. Gradually make all tests pass and not flaky and enable them back on
presubmit
Bug: 142828227
Change-Id: I6ea3d53771503e8fd968555bb2e4cb1be10d83ef
The test case testDragCustomShortcut was created initially to prevent future regression on custom shortcut (b/141568904), which was caused by ag/9342399.
Some times after ag/9342399 was reverted on ub-launcher3-master, a different error is causing custom shortcut to not working intermittently (b/141528961). Since this is different from b/141568904, it should not be a blocker to merging to master.
Bug: 141568904
Change-Id: Ia11e1ae44d0ef86c16876c002954aa662f1edbc8
this integration test help us catching app crashes when adding shortcut
widgets to the workplace. see b/141568904 for more context.
Bug: 141934188
Change-Id: I4d33d6127793efe2071d0d146aef24db6b676360
This CL adds a very low risk because most (but not all) changes affect
only Launcher behavior during the test.
This should fix a lab-only flake when all apps keeps changing while
the test is working with it.
Example: test figures out which icon to click, by the moment it clicks
there, there is another icon there, or the icon is under the search box,
and clicking opens IME.
Switching test devices to airplane mode didn't help. The earlier change
that prevents popup menu cancellation is not general enough.
Now the tests are given an API to explicitly freeze and unfreeze
all-apps, which should be a final solution.
Bug: 132900132
Bug: 133765434
Change-Id: I8b81cc9be004482beb6cdcdd05406e2d9b4c7629
Constructor of PredictionUiStateManager posts an action in 5 sec, which
may interfere with the process of opening all apps.
Waiting until the posted action happens.
Hopefully this will fix massive flakes.
Bug: 131854153
Change-Id: I6544eae1a3b063c03e78185826c05a76add1f71b
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
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
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