Now failures can be automatically directed to the correct buganizer components and forwarded directly to the correct assignees, instead of being all created into the Winscope for further triage
Test: check owners file
Change-Id: I6876a702b4f46443328aab027f7fee994b2bb819
- and update some test assumptions accordingly (live tile)
Bug: 185934639
Test: ReOpenImeWindowTest
Change-Id: If6f40dce174bef5ccc3c3731764607a5826b4762
The tests have been stable since last week when the underlying bugs were closed.
Bug: 185401242
Bug: 185400889
Test: atest FlickerTests:com.android.server.wm.flicker.ime
Change-Id: I8cea435a9fa295626c45d9d11549c1a4d4f4e63b
The tests have been stable since last week when the underlying bugs were closed.
Bug: 185401242
Bug: 185400889
Test: atest FlickerTests:com.android.server.wm.flicker.launch
Change-Id: I8ef26ac7144766f7269bef2589842e07d098efc3
The tests have been stable since last weeks when the underlying bugs were closed.
Bug: 185401242
Bug: 185400889
Test: atest FlickerTests:com.android.server.wm.flicker.rotation
Change-Id: I4aa13016f214f99bcff5adcd98e71096eacada2d
The tests have been stable since last weeks when the underlying bugs were closed.
Bug: 185401242
Bug: 185400889
Test: atest FlickerTests:com.android.server.wm.flicker
Change-Id: I6c99e84f0da01c122d8ff6a28eebbdb9bcc6582a
The flicker test suite grew and now trigger a treehuger SLO violation. To address this problem create different groups for different tests using: --module-arg <TEST SUITE>:include-annotation:<GROUP>
Where:
<TEST SUITE> = FlickerTests or WMShellFlickerTests
<GROUP> = com.android.server.wm.flicker.annotation.Group1 or com.android.server.wm.flicker.annotation.Group2 or com.android.server.wm.flicker.annotation.Group3
For example:
1) to run only tests in the first group in flicker use: `--module-arg FlickerTests:include-annotation:com.android.server.wm.flicker.annotation.Group1`
2) to run only the third group of tests from wmshell flicker: ``--module-arg FlickerTests:include-annotation:com.android.server.wm.flicker.annotation.Group3`
Bug: 180620475
Test: atest FlickerTests WMShellFlickerTests with the respective parameters
Change-Id: I82f668713ba262bafe2758e2c618bfc060cc2c8a
Some tests are still flaky and affecting presubmit
Bug: 185400889
Test: atest FlickerTests WMShellFlickerTests
Change-Id: I477799646791c69b71c6f29d71e87caba900a983
Some tests are still flaky and affecting presubmit
Bug: 185400889
Bug: 186119282
Bug: 186115871
Test: atest FlickerTests WMShellFlickerTests
Change-Id: Ie4e21d01d5ea7586f88470543321ce26ed74afa6
Previously Winscope considered only the `isVisible` property to determine if the window was visible or not. This failed in cases such as `com.google.android.googlequicksearchbox/android.app.ContextImpl` when launching apps, where `isVisible=true` and `alpha=0`
Bug: 181630910
Bug: 182720234
Test: atest FlickerTests WMShellFlickerTests
Change-Id: I75fab0c6de02e43265002986901353f8e230baa5
Previously some assertions didn't run on the whole trace because of a missing `forAllEntries` statement in the library. When activating this statement these tests fail and should be disabled.
Test: atest FlickerTests WMShellFlickerTests
Bug: 183547024
Bug: 181630910
Change-Id: I28f92e2d9de1a5465a4da5971c438bc4c0b311f9
The method was ignored before and now should be activated to enable 3 button mode. Some tests become flaky in 3-button mode and should be disabled for the moment.
Test: atest FlickerTests WMShellFlickerTests
Bug: 162925924
Change-Id: Ife24ad85c302da6fc193f1a5a226722cfed51b2b
Currently the only test is not stopping existing apps and may be affected by previous runs on the same device.
Now, ensure all apps are closed when launching the test
Bug: 167521849
Test: atest FlickerTests:com.android.server.wm.flicker.launch
Change-Id: Ib29fb4835cd728e5855ae66452ff1ac9333499ed
Ensures no other tasks are executing (cleanup) when a flicker test states to mitigate flakiness
Test: atest FlickerTests WMShellFlickerTests
Bug: 162925924
Change-Id: I84f712c8aba13ac845b9467f6c9753bc91e21a27
Add SwitchImeWindowsFromGestureNavTest in FlickerTests to support
verifying flickers when switching IME app tasks with 2-Buttons or
gestural navigation.
Fix: 181832209
Test: atest FlickerTests:SwitchImeWindowsFromGestureNavTest
Change-Id: I677d08543c75746f1405b50eab9061befeb75fc3
In several flicker tests it is necessary to check if a window or layer position is moving or resizing.
To facilitate these checks this CL introduces RectSubject (accessible through WindowStateSubject and LayerSubject) to assert rectangle behaviors
Bug: 174238224
Test: atest FlickerTests WMShellFlickerTests
Change-Id: Id568fd9dbd59f176eeb84323c321553221932685
To display additional error information, these assertions should be tests and not part of the transition.
Test: atest FlickerTests WMShellFlickerTests
Bug: 162925924
Change-Id: I94bd751a37487af49f9b12e55fce60305367200a
These flaky tests have been stable for the past week and can be promoted
Test: atest FlickerTests:com.android.server.wm.flicker.ime
Bug: 171049649
Bug: 167521849
Change-Id: Iae35556c20ce2928b36fd1dfdcdf80633e802dba
These flaky tests have been stable for the past week and can be promoted
Test: atest FlickerTests:com.android.server.wm.flicker.rotation
Bug: 171049719
Bug: 167521849
Change-Id: Iebe3abe89857e96d1985ab3f840e92fa7b168844
These flaky tests have been stable for the past week and can be promoted
Test: atest FlickerTests:com.android.server.wm.flicker.close
Bug: 171049683
Bug: 171049760
Bug: 167521849
Change-Id: I8fb98f3c9a4866bd82e2e39fb90b861719401960
These flaky tests have been stable for the past week and can be promoted
Test: atest FlickerTests:com.android.server.wm.flicker.close
Bug: 171049778
Bug: 171049647
Bug: 167521849
Change-Id: Ic7e45a27120f69b4a4d5e5ca9266809fcd969939
Tests now run in:
- Portrait + 3 Button
- Landscape + 3 Button
- Portrait + Gestural
- Landscape + Gestural
Moreover, the tests now share the code and assertions because they should behave exactly the same (except for the transition)
Test: atest FlickerTests
Bug: 167521849
Change-Id: Id88514d83e40c04bce3135cccdc142a2b2745597
It is already possible to ignore windows/layers on the verification of visibleWindowsShownMoreThanOneConsecutiveEntry and visibleLayersShownMoreThanOneConsecutiveEntry. However many tests need to manually add the Snapshot and Splash Screen entries.
Those entries are not guaranteed to show for more than 1 entry, they depend on the app behavior and when the SF actually renders the information sent by WM.
This CL removes those windows by default from the verification and refactor the tests to make it easier to update in the future
Test: atest FlickerTests WMShellFlickerTests
Bug: 182720234
Change-Id: I0e3346e078515b3e9a2065256ac04696acfa59fb
By default use only Gestural navigation, but more navigation modes can now be enabled on each test
Test: atest FlickerTests
Bug: 167521849
Change-Id: Ic8dcd2390da63663b228977928925fb1e2f99ed5
