2af1cde04d
When the default display changed due to unfolded the device, the split root tasks might be changed to invisible before reporting display info changed to split component. This causing the split component didn't update split layout due to the divider bar is not "initialized" after released with stage roots changed to invisible. This makes sure to update split layout while the split is activated no matter the divider bar is initialized or not. Fix: 189726605 Test: atest WMShellUnitTests Test: check the split bounds updated properly after the device unfolded. Change-Id: I722b08116a97b8482ea6e25b60ffe71005076cd7
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