• Home
Name Date Size #Lines LOC

..--

ActivityEmbedding/04-Jul-2025-2,5231,746

AppClose/04-Jul-2025-671380

AppLaunch/04-Jul-2025-2,5021,540

FlickerService/04-Jul-2025-2,9681,791

IME/04-Jul-2025-2,4111,627

Notification/04-Jul-2025-1,340844

QuickSwitch/04-Jul-2025-1,201760

Rotation/04-Jul-2025-1,020635

res/04-Jul-2025-5419

src/com/android/server/wm/flicker/04-Jul-2025-585317

test-apps/04-Jul-2025-8,0535,206

Android.bpD04-Jul-20252.3 KiB8881

OWNERSD04-Jul-2025127 54

README.mdD04-Jul-20251 KiB2414

README.md

1# Flicker Test Library
2
3## Motivation
4This set of tests use the flickerlib from `platform_testing/libraries/flicker` to execute a set of common UI transitions to detect discontinuous or unpredictable behavior.
5
6The tests are organized in packages according to the transitions they test (e.g., `rotation`, `splitscreen`).
7
8## Adding a Test
9
10By default, tests should inherit from `TestBase` and override the variable `transition` (Kotlin) or the function `getTransition()` (Java).
11
12Inheriting from this class ensures the common assertions will be executed, namely:
13
14* all regions on the screen are covered
15* status bar is always visible
16* status bar is at the correct position at the start and end of the transition
17* nav bar is always visible
18* nav bar is at the correct position at the start and end of the transition
19
20The default tests can be disabled by overriding the respective methods and including an `@Ignore` annotation.
21
22For more examples of how a test looks like check `ChangeAppRotationTest` within the `Rotation` subdirectory.
23
24