- Removed TestProtocol.sForcePauseTimeout and
TestProtocol.REQUEST_SET_FORCE_PAUSE_TIMEOUT
- Instead, add MotionPauseDetector.TEST_HARNESS_TRIGGER_TIMEOUT, which
is used when Utilities.IS_RUNNING_IN_TEST_HARNESS.
Test: unbundled/launcher/launcher3_test_platform
Fixes: 232548865
Change-Id: I224e99042b41375cab6bffd555434217518958c5
Lab presubmits now have a limit 60 sec per test, so failing to find an expected view will result in a cryptic "Test did not run due to instrumentation issue. Run level error reported reason: 'Instrumentation did not output anything for the configured timeout. ddmlib reported error: Failed to receive adb shell test output within 600000 ms. Test may have timed out, or adb connection to device became unresponsive.'"
Reducing the timeout to get better messages.
Bug: 236308045
Test: presubmit
Change-Id: I09e7fa02a12f4e2d0900d29b0029686337a381b0
Support move to a specific location on workspace for all workspaceDragSource, so other workspaceDragSource such as HomeAppIconMenuItem can be moved to a fixed location during testing to avoid ui-diff flakiess
Design doc:
https://docs.google.com/document/d/1tZWbfsv86O6UAKtHJrDBGecu-x3ac51qmWvARDg057M
Test: atest
Bug: 216189838
Change-Id: Ia6ef7338beb257d0313be17a53a9fc59ae39fdb6
(cherry picked from commit fe8fb4d137)
After uninstalling the app, it was disappearing after some time. For this reason, tryGetWorkspaceAppIcon was still returning it after the uninstall.
Fixes: 232009313
Test: atest TaplTestsLauncher3
Change-Id: I62e3a8f9a481e9786a136b6c00051c1025ab5b32
Also removing unused TAPL object.
Bug: 231615831
Test: Ran TaplTestsTaskbar with invalid package names and with delays
Change-Id: I9f21c9e263240ccf734993083a5e90f0442314ad
This is needed in order to implement a test for the unfold animation.
getWorkspaceAndHotseatIconsPositions returns map that associate icon name with its center on the screen
Test: atest TaplTestsLauncher3
Bug: 220087235
Change-Id: I254aa0c146edf4cae1c2bf5c09dec000993eb4d8
There was a bug in the framework (b/219711163) so
we needed a workaround to make the tapl test pass.
Test: Run TAPL tests
Bug: 219919285
Change-Id: I3eb4ca8c5b1d24f38330ad41b58c31c81eb01501
Way back we suspected that this would prevent Launcher restarts while the test runs, but later we seem to have found another solution.
Now the tests can sit for, like, 90 sec in this call.
So let's remove it and see what happens.
Test: presubmit
Bug: 187761685
Change-Id: I4baa174b48151151d657e833f121b2e6daa27453
Step 1: use both new and old APIs and make sure they return the same values.
Bug: 202567877, 227307209
Test: presubmit
Change-Id: I86fbb0ca089a88b5ff787a5c353664a192fb7e79
This is a better name now that we have gestural nav.
Renaming will happen in stages, the first one being having 2 names side-by-side.
Test: presubmit
Bug: 187761685
Change-Id: Ifb15c838cc0e161d852cf6df025687e3f92d6124
- Added TAPL objects to support TAPL tests for taskbar features
- Added tests for major taskbar features: hiding/showing the taskbar, opening all apps, lauching apps and app deep shortcuts from the taskbar/all apps page, launching apps and app deep shortcuts in splitscreen
- These tests should only run for large devices
Design: go/taskbar-tapl-tests
Test: ran tests locally with invalid configurations and remotely
Bug: 215218813
Change-Id: I3c28c339707467414aa47fa633f87fa0c1fdee57
It seems if the dragging target position's X coordinate is 0
then there is a weird bug in portrait mode.
Test: atest TwoPanelWorkspaceTest
Bug: 197631877
Change-Id: I7d8702b06e5ed396814339080f8e814e9f8a6a65
TAPL was expecting pilfer upon UP in the swipe-pause-to-overview gesture.
Actual Pilfer happens earlier, which resulted in wrong sequence-mismatch diags if the gesture fails before UP.
Now expecting Pilfer earlier.
Also fixing a problem that sneaked through earlier reviews when even down time was passed incorrectly.
Bug: 187761685
Test: presubmit
Change-Id: If4289a011247bf7801405ecaac8befa8461e8a37
Needed because when running tests in virtual devices is very slow. The previous number of steps was also greater than the default timeout for home gesture.
Fixes 215673732
Test: atest Launcher3Tests:RequestPinItemTest
Change-Id: I9b13d97deb158222ba0ebf3f6a536c5a7ae632cf
- OOP test activity has an alertTitle and shouldn't be treated as system anomaly dialog
Fix: 214558538
Test: NexusLauncherOutOfProcTests / MemoryTests
Change-Id: Ia9c330c3c3f48b43fbada40a3410ccc9fb8bfbb8
- Somehow when home gesture's travel distance is above certain number (~2560px in the bug's case), the touch will wrongly go to the 3P launcher instead of staying in quickstep launcehr only. As it's unusal for home gesture to be so long, limiting it to half of screen height.
Bug: 214279686
Test: presbumit and TaplTestsLauncher3#testWidgets on cf_tablet
Change-Id: I1107074556aea3011b186ba34dc830dbb1445517
1. Implement function to uninstall app from appIcon.
2. Add test uninstall to TaplTestsLauncher3.
Bug: 210927656
Test: Launcher3Tests:com.android.launcher3.ui.TaplTestsLauncher3#testTryUninstallFromWorkspace
Change-Id: Iedd3bd3a46bc626fc414fd8c5bd07ebc0fa235bb
- TODO: enable test in portrait
Test: TwoPanelWorkspaceTest
Former CL: http://ag/16357467
Bug: 197631877
Change-Id: I35c326b7a6c612d2fb66c8b94b810f5131fd58d8
The display's x-coordinates for input are in the range:
[0, displayWidth).
Injecting input at the point (displayWidth, 0) is technically outside
of the display. After accounting for insets, the x-coordinate range for
the display is:
[leftInset, displayWidth - rightInset).
An input event injected at x = (displayWidth - rightInset) would be
outside of this range, and would be within the right insets region.
To account for this, use a one pixel buffer when calculating the
right gesture start margin.
A similar one pixel buffer is already used for the bottom margin
calculation.
Test: atest NexusLauncherTests:
com.android.quickstep.TaplTestsQuickstep
Bug: 208849306
Change-Id: I9d5a6429cd55fdfcbf2c849e27e3d3a0a7faaa47