- Open IME from fixed orientation
- Open IME to overview
Bug: 224407658
Bug: 227189877
Test: atest FlickerTests:com.android.server.wm.flicker.ime
Change-Id: I814720b6998ae06638962fab3b7daaaf30982e5e
Reduce the flakness caused from remove window animation, the snapshot
starting window with IME window could stay on screen longer.
Bug: 226684870
Test: atest FlickerTests:SwitchImeWindowsFromGestureNavTest
Change-Id: I247a718d637f0b2d5c05210f670289dcae5968a5
At the moment, when launching an app over the lock screen, the navbar flickers. During the animation it:
- appears
- disappears
- reappears
Bug: 227072573
Test: atest OpenAppNonResizeableTest
Change-Id: I17dd8f8ff70c4c12db97d6f337f1500e0ab177d0
Making sure CL[1] can resolve IME flickers when
- App with IME transiting from a fixed orientation task
- App with IME transiting to the overview screen
[1]: I332c0e4fff62df5d7b793eda2767bb58fe85a938
Fix: 224407658
Test: atest FlickerTests:OpenImeWindowFromFixedOrientationAppTest
Test: atest FlickerTests:OpenImeWindowToOverViewTest
Change-Id: I3120d403b850418a87f57472b91674b0165982b0
Looking at the dashboard all these tests are fairly reliable now pretty much always green
Test: atest FlickerTests:QuickSwitchFromLauncherTest FlickerTests:QuickSwitchBetweenTwoAppsBackTest FlickerTests:QuickSwitchBetweenTwoAppsForwardTest
Change-Id: Ifc9e042439aa436497d3f4e2e7df94ba0f30a14b
The navbar vanishes and reappears during the transition. Wait until the navbar appears to consider the transition finished.
Bug: 219690120
Bug: 220083329
Test: atest WMShellFlickerTests
Change-Id: Ib4514872fa8e9c2eac4148095474d26255f4a712
This makes triaging issues unrelated to the test (e.g., transition crash) easier since all failing assertions are clustered with the same stack trace
Bug: 219773854
Test: atest FlickerTests WMShellFlickerTests
Change-Id: I65bb1b5e87997c856ce080b24d549ba1c978955a
Merged-In: I65bb1b5e87997c856ce080b24d549ba1c978955a
Fixes problem with rotationLayerAppearsAndVanishes_shellTransit calling rotationLayerAppearsAndVanishes which included the assertion along with an Assume.assumeFalse(isShellTransitionsEnabled) which meant the test would never run
Test: atest FlickerTests:ChangeAppRotationTest
Change-Id: Icf637f09a062e5f56cab4b5b28fbba7208b0fea4
Since added OpenAppFromOverviewTest_ShellTransit any tests in OpenAppFromOverviewTest that are split between shell and non shell become redundant
Test: atest FlickerTests:OpenAppFromOverviewTest FlickerTests:OpenAppFromOverviewTest_ShellTransit
Change-Id: Ic4a53d969d2d62457c3d98d98090af0b942d03c8
Using compressed trace files speeds up trace collection and the benefits of using async trace fetch become negligible.
To simplify the code, remove the functionality
Bug: 209843622
Test: atest FlickerTests WMShellFlickerTests
Change-Id: Id21d58af5393eb7f364b353db619c55a5a5b616c
Create specific class for shell transition when whole CUJ crashes
Bug: 209843622
Test: atest FlickerTests WMShellFlickerTests
Change-Id: I8d3d96af7303e6bd7bc4a540aa79b0f9ea3bf4a0
We run the flicker tests multiple times to detect CLs that intoruce flakiness early. Currently we run 5 executions of each CUJ. However, due to lab capacity and impact in presubmit times, this CL reduces the repetitions to 3
Bug: 209843622
Test: atest FlickerTests WMShellFlickerTests
Change-Id: I165937fb82953d62c028ffe96a948d0ca00dbbe2
OpenAppNonResizeableTest was inheriting from OpenAppTransition which specified assertions assuming the app was launched from the launcher but that isn't the case there, we launch from the lock screen
Test: atest FlickerTests:OpenAppColdTest FlickerTests:OpenAppFromOverviewTest FlickerTests:OpenAppNonResizeableTest
Bug: 213856453
Change-Id: I4bc1eca68598471452e4cac94903f0d92dba635b
Assertions are very flaky, don't provide any immediately useful information in the current state and going to be replace soon anyways
Test: atest FlickerTests
Change-Id: Id8f7649b818237bc16051d808ef46ca875669faa
Otherwise its WidowManager.LayoutParams#windowAnimations is 0, then
it won't play animation (TransitionAnimation#loadAnimationAttr
returns null) so the the surface of closing app may be updated to
invisible at random timing that causes the test flaky.
Use darker gray as window background color to make it easier to
distinguish the visual result between home, starting window (gray)
and app content (orange).
Bug: 216297992
Bug: 213852103
Test: com.android.server.wm.flicker.launch.OpenAppColdTest
Change-Id: I3bb073dfa52484a63168b3aeb6e7f5f43bd02aac
Due to the large amount of traces on flicker, the tests take 15min+ to copy the files from the device to the host after the test execution. Instead, start copying the files asynchronously.
It is not possible to use the async mechanism from Tradefed's FilePullerLogCollector because it either: (1) pushes the files form the directory multiple times -- once per test -- creating a lot of duplicates; or (2) cleans up the directory without checking for new files, losing some files.
This CL creates an asynchronous file upload mechanism for flicker using coroutines
Bug: 216111397
Test: atest FlickerTests WMShellFlickerTests
Change-Id: I5bbae834cf3439950626823c6b665c733e27e517
Currently we launch the activity for each iteration and that is not necessary. The test hsould launch it once
Bug: 209843622
Test: atest FlickerTests
Change-Id: Ibce9f17954771158cb6d85b213f40a215f0c0c30
So that we can keep track of the status, and move it back to presubmit
after it becomes stable
Bug: 214452854
Test: pass existing
Change-Id: I60453789676cda9eb0892b601806d398af7bdc82
