Files

Hongwei Wang e4f4f107f3 Reset PiP shadow radius in onTaskVanished

This is a follow-up of ag/17527240 in which we do not cover the case
that a Task in pinned mode is directly removed via Task#moveTaskToBack

Video: http://recall/-/aaaaaabFQoRHlzixHdtY/cMG5Uh1kLC7EyAs2EbDVkM
Bug: 228793904
Test: follow the reproduce step in bug, see video
Test: atest WMShellUnitTests:PipTaskOrganizerTest
Change-Id: Ib7472908a81d56d34216ca272afbd9f1a2668b89

2022-04-15 13:51:30 -07:00

flicker

Remove references to old FaaS test rule

2022-04-13 09:38:26 +00:00

unittest

Reset PiP shadow radius in onTaskVanished

2022-04-15 13:51:30 -07:00

OWNERS

Merge "Update component ids from Winscope to Flicker" am: d41316339d am: 1016b2d3c2 am: b9a97d8d9b

2022-04-05 15:19:51 +00:00

README.md

…

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