Files

Bill Lin 801a654427 Do not access SettingProvider in test code

New policy: b/175024829
Settings key: <one_handed_*> is not readable.
From S+, new public settings keys need to be annotated
with @Readable unless they are annotated with @hide.

Recent changes :
ag/13764747 Remove @Readable for hidden fields added in S

Test: atest WMShellUnitTests
Bug: 183064974
Change-Id: I185491189a3804d7038be3c117583ab571e7a961

2021-03-18 15:07:15 +08:00

flicker

Remove Snapshot and Splash Screen from consecutive entry check

2021-03-16 10:26:55 +01:00

unittest

Do not access SettingProvider in test code

2021-03-18 15:07:15 +08:00

OWNERS

Include component ID in OWNERS file

2021-02-18 09:35:06 +00:00

README.md

Add flicker test for WM Shell

2020-08-20 16:13:57 -07:00

README.md

WM Shell Test

This contains all tests written for WM (WindowManager) Shell and it's currently divided into 3 categories

unittest, tests against individual functions, usually @SmallTest and do not require UI automation nor real device to run
integration, this maybe a mix of functional and integration tests. Contains tests verify the WM Shell as a whole, like talking to WM core. This usually involves mocking the window manager service or even talking to the real one. Due to this nature, test cases in this package is normally annotated as @LargeTest and runs with UI automation on real device
flicker, similar to functional tests with its sole focus on flickerness. See WM Shell Flicker Test Package for more details