Debuggable reamdump data collection dialog is triggering up while
running tests. These are causing flakes. While a better fix would be
figuring out why these are triaggered, the wm tests should be
independent of internal apps which an end user of Android won't see.
Test: Forrest
Bug: 258578781
Bug: 239384214
Change-Id: Ia4c0c670fe3e35f84640787cb8fce70e74edb264
This reverts commit 7c5f0e8e64.
Reason for revert: Landing feature again. We need a larger buffer for flicker detection
Fixes: 255715397
Change-Id: I5e51ae254b94eacd5751a04a03991147aa19154a
This reverts commit 3bedae5d01.
Reason for revert: Significantly increased flakiness in go/wm-tests-flicker
Change-Id: I8e1e051103029abf1b431d514b24a7b6253599b9
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
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
Because of the configuration file split we no longer need to reboot the device at the end of flicker tests - this will speed up the time required to get the final results from tests.
Test: atest FlickerTests WMShellFlickerTests
Bug: 206633034
Change-Id: I76285ca64aa7a8913088e625999d5756a2e662a0
Logging all transactions of WM lead to logging inconsistent states that are not sent to SF nor visible to the end user. This information increases the flakiness of the test.
Logging only on frame means that the log will only contain the information sent to SF.
Test: atest FlickerTests WMShellFlickerTests
Bug: 167521849
Change-Id: I16624181ebd127482724439fff84d4bca7fe9ab3
Atest cannot override include-annotation and exclude-annotation from the Android.xml, only append new ones.
Ideally we should have a single test configuration for all flicker tests (presubmit/postsubmit/flaky) and adjust the arguments according to the type of test we intend to run.
Presubmit:
atest FlickerTests -- --module-arg FlickerTests:include-annotation:android.platform.test.annotations.Presubmit --module-arg FlickerTests:exclude-annotation:androidx.test.filters.FlakyTest
Postsubmit:
atest FlickerTests -- --module-arg FlickerTests:include-annotation:android.platform.test.annotations.Postsubmit --module-arg FlickerTests:exclude-annotation:androidx.test.filters.FlakyTest
Flaky:
atest FlickerTests -- --module-arg FlickerTests:include-annotation:androidx.test.filters.FlakyTest
To run WMShellFlickerTests, just replace FlickerTests for WMShellFlickerTests in the commands above.
Bug: 170490377
Test: atest FlickerTests WMShellFlickerTests
Change-Id: Ic252f27065714e9039e3c0f33659b98eb288aa6f
Enable tests ot be in presubmit, postsubmit or marked as flaky
Do not require flicker DSL changes
Bug: 162923992
Test: atest FlickerTests WMShellFlickerTests
Change-Id: I74fdadaf5f6f08d96973683682297200eec6658d
Previously the flickerlib had some pixel specific code, now it's
general. All pixel specific code either should migrate to FlickerTests
or to flickerlib-helpers
Test: atest FlickerTests
Change-Id: Ibca99f2bf68a511f73130439f6334a01e47a8671
Separated folders in libs/WindowManager/Shell/tests
- unittest, for unit tests
- flicker, for this flicker tests
- propose to add functional/ folder for functional tests
Note also
- Copied over EnterPipTest from existing flicker tests as proof of
concept
- TODO: need to figure out the next step for the flicker test library
itself as it's currently packaged in com.android.server.wm
Bug: 161561007
Test: atest WMShellFlickerTests
Test: atest WMShellUnitTests
Change-Id: Ic06e7cb0f98151591ccb9f5217260939349a9aa5
