Files

Chris Li 29f24a134c DisplayContent rotateBounds not keeping same physical position for 180

Rotation_90 + rotation_90 is different from the result of rotation_180
with the current implementation. Should also take care of rotation_180.

Fix: 180751251
Bug: 173124775
Test: atest WmTests:DisplayContentTests
Test: atest WMShellUnitTests:DisplayLayoutTest
Test: atest FrameworksCoreTests:RotationUtilsTest
Change-Id: Ia1c87409b4c4cc412c3fd89e58d08b6ae2069fd0

2021-02-23 17:34:26 -08:00

flicker

Use FlickerParametersRunnerFactory

2021-02-23 16:06:17 +01:00

unittest

DisplayContent rotateBounds not keeping same physical position for 180

2021-02-23 17:34:26 -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