drgreen/android_frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
android_frameworks_base/tests/FlickerTests/AndroidTest.xml

36 lines
1.8 KiB
XML
Raw Normal View History

Move FlickerTests to frameworks/base/tests 2/2 platform_testing is moving to AOSP first development. FlickerTests may require access to in development test apis and cannot be developed in AOSP. Other minor changes: - remove FlickerTests from APCT. FlickerTests will use TEST_MAPPING - use @FlakyTest instead of @Ignore annotation to skip tests Test: atest FlickerTests Test: make -j32 continuous_instrumentation_tests Test: cd frameworks/base/tests/FlickerTests/ && atest :postsubmit Bug: 112044297 Change-Id: Icc3194ddd9b801034d8797bf2ec60ebff071612c
2018-08-01 10:13:36 -07:00
<?xml version="1.0" encoding="utf-8"?>
<!--
* Copyright 2018 Google Inc. All Rights Reserved.
-->
<configuration description="Runs WindowManager Flicker Tests">
<option name="test-tag" value="FlickerTests" />
Replace GoogleDeviceSetup with DeviceSetup in FlickerTests This commit replaces GoogleDeviceSetup which is not on AOSP. Test: atest FlickerTests Bug: 128877715 Change-Id: I2e4167dd7e4e5ef3352cb8fda2f753a0acf2f600
2019-03-19 13:20:53 +08:00
<target_preparer class="com.android.tradefed.targetprep.DeviceSetup">
Move FlickerTests to frameworks/base/tests 2/2 platform_testing is moving to AOSP first development. FlickerTests may require access to in development test apis and cannot be developed in AOSP. Other minor changes: - remove FlickerTests from APCT. FlickerTests will use TEST_MAPPING - use @FlakyTest instead of @Ignore annotation to skip tests Test: atest FlickerTests Test: make -j32 continuous_instrumentation_tests Test: cd frameworks/base/tests/FlickerTests/ && atest :postsubmit Bug: 112044297 Change-Id: Icc3194ddd9b801034d8797bf2ec60ebff071612c
2018-08-01 10:13:36 -07:00
<!-- keeps the screen on during tests -->
<option name="screen-always-on" value="on" />
<!-- prevents the phone from restarting -->
<option name="force-skip-system-props" value="true" />
New FlickerTests: Create initial flicker tests for Pip Create an initial set of tests for pip. Initial tests are: - All regions covered - Status and navigation bar is always visible - Pip window is shown, expanded, closed, and doesn't flicker - Pip layer is shown, expanded, closed, and doesn't flicker - Background is displayed behind Pip window Test: atest FlickerTests:PipToHomeTest and atest FlickerTests:PipToAppTest Change-Id: I16345de39a799744b97a5390495538d568693222
2019-09-25 17:12:40 +02:00
<!-- set WM tracing verbose level to all -->
Enable test harness flag before the test The test harness must be enabled to alllow the test to interact with TAPL (launcher), otherwise the test crashes with an "Error granting runtime permission" exception. Test: atest FlickerTests Change-Id: I5fffa4e756fab7ab4abca8a4d301f3c01e1297ce
2020-03-30 11:19:29 +02:00
<option name="run-command" value="cmd window tracing level all" />
Log WM trace on frame instead of transaction 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
2021-03-05 15:52:05 +01:00
<!-- set WM tracing to frame (avoid incomplete states) -->
<option name="run-command" value="cmd window tracing frame" />
Revert "Use RunHostCommandTargetPreparer to enable TAPL" This reverts commit e7e97b72742675ef7139768349ca40d4c5eb4b18. Reason for revert: While this command works locally (atest) on all build types, it does not work when multiple devices are simultaneously connected to the computer Change-Id: I9744d02f0eafe2fef3076c62cd07a8cac05546da
2020-04-21 16:36:00 +00:00
<!-- restart launcher to activate TAPL -->
<option name="run-command" value="setprop ro.test_harness 1 ; am force-stop com.google.android.apps.nexuslauncher" />
New FlickerTests: Create initial flicker tests for Pip Create an initial set of tests for pip. Initial tests are: - All regions covered - Status and navigation bar is always visible - Pip window is shown, expanded, closed, and doesn't flicker - Pip layer is shown, expanded, closed, and doesn't flicker - Background is displayed behind Pip window Test: atest FlickerTests:PipToHomeTest and atest FlickerTests:PipToAppTest Change-Id: I16345de39a799744b97a5390495538d568693222
2019-09-25 17:12:40 +02:00
</target_preparer>
Move FlickerTests to frameworks/base/tests 2/2 platform_testing is moving to AOSP first development. FlickerTests may require access to in development test apis and cannot be developed in AOSP. Other minor changes: - remove FlickerTests from APCT. FlickerTests will use TEST_MAPPING - use @FlakyTest instead of @Ignore annotation to skip tests Test: atest FlickerTests Test: make -j32 continuous_instrumentation_tests Test: cd frameworks/base/tests/FlickerTests/ && atest :postsubmit Bug: 112044297 Change-Id: Icc3194ddd9b801034d8797bf2ec60ebff071612c
2018-08-01 10:13:36 -07:00
<target_preparer class="com.android.tradefed.targetprep.suite.SuiteApkInstaller">
<option name="cleanup-apks" value="true"/>
<option name="test-file-name" value="FlickerTests.apk"/>
<option name="test-file-name" value="FlickerTestApp.apk" />
</target_preparer>
<test class="com.android.tradefed.testtype.AndroidJUnitTest">
<option name="package" value="com.android.server.wm.flicker"/>
<option name="shell-timeout" value="6600s" />
Compatibilize tests with new runner Runner now prints each assertion individually to aid debugging. Bug: 162923992 Test: atest FlickerTests WMShellFlickerTests Change-Id: I1c9a49ec3c283e5e034f0223573fca3ccafaf64c
2020-12-15 14:36:03 +01:00
<option name="test-timeout" value="6600s" />
Move FlickerTests to frameworks/base/tests 2/2 platform_testing is moving to AOSP first development. FlickerTests may require access to in development test apis and cannot be developed in AOSP. Other minor changes: - remove FlickerTests from APCT. FlickerTests will use TEST_MAPPING - use @FlakyTest instead of @Ignore annotation to skip tests Test: atest FlickerTests Test: make -j32 continuous_instrumentation_tests Test: cd frameworks/base/tests/FlickerTests/ && atest :postsubmit Bug: 112044297 Change-Id: Icc3194ddd9b801034d8797bf2ec60ebff071612c
2018-08-01 10:13:36 -07:00
<option name="hidden-api-checks" value="false" />
</test>
<metrics_collector class="com.android.tradefed.device.metric.FilePullerLogCollector">
Store and pull files from /sdcard/ Tradefed FilePullerLogCollector can no longer access the internal app directory (e.g. /storage/emulated/0/Android/data/com.android.server.wm.flicker/files). This makes it unable to pull trace files, when a test fails. This CL makes flicker tests store their data on /sdcard/flicker which can be accessed by the Tradefed FilePullerLogCollector Bug: 171026227 Test: atest FlickerTests Change-Id: Ibed6b621b068b0668d93b39838c0959441527295
2020-12-01 16:27:22 +01:00
<option name="directory-keys" value="/sdcard/flicker" />
Move FlickerTests to frameworks/base/tests 2/2 platform_testing is moving to AOSP first development. FlickerTests may require access to in development test apis and cannot be developed in AOSP. Other minor changes: - remove FlickerTests from APCT. FlickerTests will use TEST_MAPPING - use @FlakyTest instead of @Ignore annotation to skip tests Test: atest FlickerTests Test: make -j32 continuous_instrumentation_tests Test: cd frameworks/base/tests/FlickerTests/ && atest :postsubmit Bug: 112044297 Change-Id: Icc3194ddd9b801034d8797bf2ec60ebff071612c
2018-08-01 10:13:36 -07:00
<option name="collect-on-run-ended-only" value="true" />
Automatically clean up flicker test data Currently the flicker tests leave data on the /sdcard/flicker directory. We now clean up this data after the test. The logs are still available in the atest results directory. Test: atest FlickerTests Change-Id: Ia83cbedff3104964e3d4be14a7c035f2193d36a8
2019-12-04 09:23:34 +01:00
<option name="clean-up" value="true" />
Move FlickerTests to frameworks/base/tests 2/2 platform_testing is moving to AOSP first development. FlickerTests may require access to in development test apis and cannot be developed in AOSP. Other minor changes: - remove FlickerTests from APCT. FlickerTests will use TEST_MAPPING - use @FlakyTest instead of @Ignore annotation to skip tests Test: atest FlickerTests Test: make -j32 continuous_instrumentation_tests Test: cd frameworks/base/tests/FlickerTests/ && atest :postsubmit Bug: 112044297 Change-Id: Icc3194ddd9b801034d8797bf2ec60ebff071612c
2018-08-01 10:13:36 -07:00
</metrics_collector>
</configuration>
Reference in New Issue Copy Permalink