Files

wilsonshih 7a7722abe0 Correcting the package name used on splash screen window.

The top activity in TaskActivitiesReport can be filter out if the state
of top activity is INITIALIZING, this doesn't make sense for splash
screen, because the state of the top activity do can be INITIALIZING.
Create a filed targetActivityInfo in StartingWindowInfo to specify the
starting activity info.

Bug: 193459277
Test: atest SplashscreenTests StartingSurfaceDrawerTests
Change-Id: Ifec7aff644013a0426e0622162ab24f6b9fb3d8f

2021-07-23 16:50:01 +08:00

flicker

Merge "Split flicker tests into groups" into sc-dev

2021-05-22 09:44:36 +00:00

unittest

Correcting the package name used on splash screen window.

2021-07-23 16:50:01 +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