diff options
| author | 2025-02-18 17:20:47 +0000 | |
|---|---|---|
| committer | 2025-02-18 09:40:59 -0800 | |
| commit | af9338987fd36e97c9e17ad62a8ef2b3e63c821e (patch) | |
| tree | 8bd0069502113845ff2e280ad077ea6fc4a09b39 /api/coverage/tools | |
| parent | 32d0aba7574e2fd77f09e41d94c6b1f00da2b903 (diff) | |
[SB][Chip] Add annotations to enable/disable ChipsModernization in test
I frequently find myself writing
`@EnableFlags(StatusBarChipsModernization.FLAG_NAME)` in a test without
remembering to also enable StatusBarRootModernization, which
ChipsModernization is dependent on. This can cause test failures like
b/396595475 which are non-obvious.
This CL marks StatusBarChipsModernization.FLAG_NAME as deprecated to
discourage people from using it directly in tests and instead adds two
test annotations that should be used instead:
- @EnableChipsModernization enables both ChipsModernization &
RootModernization
- @DisableChipsModernization that disables just ChipsModernization
This CL updates some test classes to use the new annotations, other test
classes will be updated in the next CL.
Bug: 372657935
Bug: 396595475
Flag: com.android.systemui.status_bar_chips_modernization
Test: atest OngoingActivityChipsWithNotifsViewModelTest
Change-Id: Ibafc7055f8bdda9766d8ab9e831af56fbe8ab243
Diffstat (limited to 'api/coverage/tools')
0 files changed, 0 insertions, 0 deletions