Files

wilsonshih 11af33eeaf Fix several test failures for the new starting window.(10/N)

1. Register TestStartingWindowOrganizer to mock add/remove starting
window.
2. Do not show starting window if not occluded.
3. Add ReadFrameBuffer permission so Car can get TaskSnapshot.
4. Correct package path for shell.startingsurface.
5. Do not show starting window for home type.

Bug: 73289295
Bug: 131311659

Test: atest TaplTestsLauncher3
Test: atest WmTests StartingSurfaceDrawerTests TaskSnapshotWindowTest
Test: atest CtsWindowManagerDeviceTestCases
Change-Id: I89930d2e8a05cca6197c36c780ee1843fe454354

2021-03-12 04:08:56 +00:00

flicker

Merge "Update PIP menu accessiblity bounds when it is moved" into sc-dev

2021-03-10 23:51:52 +00:00

unittest

Fix several test failures for the new starting window.(10/N)

2021-03-12 04:08:56 +00: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